[eslint-monster] actions/setup/js lint remediation dispatch - 2026-08-05

[github-actions[bot]]

Summary

ESLint factory reported 73 warnings under actions/setup/js in today's run. I grouped the actionable work into three existing remediation streams and dispatched Copilot to each.

Remediation streams

1. Unsafe catch-property access

• Tracking issue: [eslint-monster] setup/js: fix unsafe catch-property access and dynamic pattern construction warnings #49215
• Affected files from today's run: check_permissions_utils.cjs, checkout_manifest.cjs, dismiss_pull_request_review.cjs, frontmatter_hash_pure.cjs, mcp_server_core.cjs, pick_experiment.cjs, push_repo_memory.cjs, remove_trigger_label.cjs, resolve_mentions_from_payload.cjs, write_large_content_to_file.cjs
• Representative diagnostics:
  • check_permissions_utils.cjs:210 unsafe .status on caught botError
  • dismiss_pull_request_review.cjs:238 unsafe .status / .message on caught getReviewError
  • frontmatter_hash_pure.cjs:719 unsafe .status on caught error
• Expected outcome: narrow caught values before reading .status, .code, .message, or similar properties, then validate with npm run lint:setup-js.

2. Runtime-hardening / unhandled-throw guards

• Tracking issue: [eslint-monster] setup/js: harden unhandled throw sites (fetch/fs/JSON.parse/execSync/async entrypoints) #49214
• Affected files from today's run: data_schema_normalizer.cjs, exchange_otlp_workload_identity.cjs, generate_usage_activity_summary.cjs, start_mcp_gateway.cjs, test-live-github-api.cjs, upload_artifact.cjs, validate_memory_files.cjs
• Representative diagnostics:
  • data_schema_normalizer.cjs:155 wrap JSON.parse(rawSchema) in try/catch
  • exchange_otlp_workload_identity.cjs:23 and :50 wrap fetch(...) in try/catch and add timeout signal
  • start_mcp_gateway.cjs:880 wrap execSync(...) in try/catch
• Expected outcome: add local guards around throwing APIs so failures are reported cleanly, then run npm run lint:setup-js.

3. Caught-error formatting hygiene

• Tracking issue: [eslint-monster] setup/js: replace unsafe caught-error stringification and interpolation #49213
• Affected files from today's run: copilot_harness.cjs, copilot_sdk_driver.cjs, create_issue.cjs, mcp_server_core.cjs, parse_mcp_scripts_logs.cjs, parse_token_usage.cjs, pi_agent_core_driver.cjs
• Representative diagnostics:
  • copilot_harness.cjs:860 unsafe ${parseErr} interpolation
  • copilot_sdk_driver.cjs:148 err.stack ? err.stack : String(err) fallback
  • create_issue.cjs:1192 prefer getErrorMessage(error)
• Expected outcome: replace noisy/unsafe caught-error formatting with getErrorMessage(...) where available, then run npm run lint:setup-js.

Notes

• An existing fourth issue, [eslint-monster] actions/setup/js: escape dynamic RegExp interpolations #49669, already covers the separate dynamic-RegExp escaping cluster; it was not re-assigned to stay within the 3-assignment limit.
• Attempted issue-body refreshes via safeoutputs update_issue, but this workflow configuration only permits issue-context updates on triggering issues, so dispatch proceeded using the existing tracking issues plus new assignments.

Run: https://github.com/github/gh-aw/actions/runs/31052158731

Generated by 🧹 ESLint Monster · gpt54 · 16.3 AIC · ⌖ 5.71 AIC · ⊞ 5K · ◷

• expires on Aug 7, 2026, 2:24 PM UTC-08:00

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-08-07T22:24:40.487Z.

Closed by Workflow