-
Notifications
You must be signed in to change notification settings - Fork 639
chore: Bump @metamask/eslint-config from 14.0.0 to 15.0.0 #3762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -76,7 +76,7 @@ | |
| "@lavamoat/allow-scripts": "^3.4.0", | ||
| "@metamask/auto-changelog": "^5.0.2", | ||
| "@metamask/create-release-branch": "^4.1.3", | ||
| "@metamask/eslint-config": "^14.0.0", | ||
| "@metamask/eslint-config": "^15.0.0", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: Peer dependency mismatch for eslint config related packagesBumping Additional Locations (1) |
||
| "@metamask/eslint-config-browser": "^14.0.0", | ||
| "@metamask/eslint-config-jest": "^14.0.0", | ||
| "@metamask/eslint-config-nodejs": "^14.0.0", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Peer dependency mismatch with related eslint-config packages
Bumping
@metamask/eslint-configto^15.0.0creates peer dependency conflicts. The companion packages (@metamask/eslint-config-browser,@metamask/eslint-config-jest,@metamask/eslint-config-nodejs,@metamask/eslint-config-typescript) remain at^14.0.0, but they declare@metamask/eslint-config: ^14.0.0as a peer dependency. According to the release notes, v15.0.0 versions of these companion packages exist specifically to update this peer dependency requirement. This mismatch will cause npm/yarn peer dependency warnings or errors and could lead to unexpected ESLint configuration behavior.