[eslint-monster] [ESLint Monster] setup/js remediation plan - 2026-07-30

[github-actions[bot]]

Daily npm run lint:setup-js reported 153 warnings in actions/setup/js, grouped into three remediation streams and assigned to Copilot.

Streams launched

1. [detection-analysis] Detection Analysis Report — 2026-07-29 #49009 — replace unsafe caught-error stringification and interpolation

   • Focus: String(err), ${err}, and err.stack fallback patterns where getErrorMessage(...) should be used.
   • Validation: npm run lint:setup-js

2. update_project: numeric fields are inferred as SINGLE_SELECT and skipped #49010 — harden unhandled throw sites

   • Focus: missing try/catch around fetch, JSON.parse, execSync, sync fs calls, and async entrypoint .catch(...) handling.
   • Validation: npm run lint:setup-js

3. [pr-sous-chef] PR Sous Chef run report #49011 — fix unsafe catch-property access and dynamic pattern construction

   • Focus: direct property reads from caught values, regex interpolation escaping, and interpolated process-command construction.
   • Validation: npm run lint:setup-js

Triage notes

• Scope kept strictly under actions/setup/js.
• Assignments capped at three streams as requested.
• Representative lint rules included in each issue body for direct implementation guidance.

Generated by 🧹 ESLint Monster · gpt54 · 15.8 AIC · ⌖ 6.66 AIC · ⊞ 4.8K · ◷

• expires on Aug 1, 2026, 2:22 PM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by ESLint Monster.

A newer discussion is available at Discussion #49671.