Skip to content

Add CI workflow to verify ESLint config on dependency upgrades#25232

Draft
dennisoelkers wants to merge 1 commit intomasterfrom
feat/eslint-upgrade-check
Draft

Add CI workflow to verify ESLint config on dependency upgrades#25232
dennisoelkers wants to merge 1 commit intomasterfrom
feat/eslint-upgrade-check

Conversation

@dennisoelkers
Copy link
Member

@dennisoelkers dennisoelkers commented Mar 5, 2026

Description

Motivation and Context

Catches broken ESLint configurations (exit code 2) when PRs modify
eslint dependencies, config, or plugin packages, while allowing
expected lint issues (exit code 1) to pass.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

/nocl No user-facing change.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Refactoring (non-breaking change)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have requested a documentation update.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.

Catches broken ESLint configurations (exit code 2) when PRs modify
eslint dependencies, config, or plugin packages, while allowing
expected lint issues (exit code 1) to pass.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant