Guard lint tooling compatibility - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Dependabot proposed ESLint 10 even though it requires Node 20.19 or newer and MMM-MessageCenter currently supports Node 18. The existing workflow installed the incompatible development dependency with warnings but never invoked it, allowing the checks to appear successful.
Impact
ESLint remains on the compatible 9.x line while Node 18 is supported. Future lint-tool incompatibilities will fail CI instead of passing unnoticed.
Validation
npm run lintnpm test— 87 passing testsgit diff --check