Consolidate dependabot PRs #116, #121, #122, #123, #124, #125 into single working upgrade

[Copilot]

Six dependabot PRs were individually failing CI due to peer dependency conflicts (notably @typescript-eslint parser/plugin needing matching major versions) and ESLint 9 requiring flat config format.

Changes

• @typescript-eslint/eslint-plugin + @typescript-eslint/parser: ^6.21 → ^8 (v8 required for ESLint 9 peer compat; resolves PRs Bump @typescript-eslint/eslint-plugin from 6.21.0 to 7.0.0 #116, Bump @typescript-eslint/parser from 6.21.0 to 7.8.0 #122)
• eslint: ^8.56 → ^9 (PR Bump eslint from 8.56.0 to 9.1.1 #123)
• eslint-plugin-jest: ^28.3.0 → ^28.7.0 (PR Bump eslint-plugin-jest from 27.6.3 to 28.3.0 #125; ^28.7.0 is minimum supporting @typescript-eslint v8 as optional peer dep)
• @babel/core, @babel/preset-env, @babel/preset-typescript: ^7.23 → ^7.24 (PR Bump @babel/core from 7.23.9 to 7.24.5 #124)
• undici: 5.28.3 → 5.29.0 transitively (PR Bump undici from 5.28.3 to 5.28.4 #121 security fix)

Config migration

.eslintrc.js + .eslintignore replaced with eslint.config.js (flat config, required by ESLint 9):

• jest/unbound-method scoped to .ts test files only — rule requires type info unavailable in .js test files
• Added header comment documenting the migration from legacy .eslintrc.js format

Source fix

src/index.ts: refactored a ternary/&&-as-statement expression flagged by the stricter @typescript-eslint/no-unused-expressions rule in v8:

// Before
failOnMissing && !hasOverrideMissingLabels
  ? core.setFailed(message)
  : createWarnings && core.warning(message);

// After
if (failOnMissing && !hasOverrideMissingLabels) {
  core.setFailed(message);
} else if (createWarnings) {
  core.warning(message);
}

CI fix

The integrations-* test jobs require a work item reference (using a resolve keyword) to be present in both the PR description and a commit message. Added resolve -> FAKE-1234 to the PR description and included it in a commit message to satisfy the tests that check PR context (find-in-pr-context, find-in-ref-commits, find-in-branch) as well as commits (find-in-pr-commits uses include-pr: false, include-commits: true).

Don't remove

Include work item for tests to pass.
resolve -> FAKE-1234

Note you must also include a work item within the commit or tests will fail using the resolve keyword as shown above.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[github-actions]

Next Version: v4.2.4

[ahernandez411]

@copilot

All the tests with integrations- in the name failed. Can you look at that?

[Copilot]

@copilot

All the tests with integrations- in the name failed. Can you look at that?

The integrations-* failures were caused by missing work item references. The tests search for resolve -> FAKE-1234 in PR commits and PR description, but neither contained it.

Fixed in commit d1415cd by:

1. Including resolve -> FAKE-1234 in the commit message (needed by integrations-pr find-in-pr-commits which uses include-pr: false, include-commits: true)
2. Including resolve -> FAKE-1234 in the PR description (needed by integrations-reference and integrations-pr find-in-pr-context which read PR title/body)