chore(deps-dev): bump @eslint/js from 9.39.4 to 10.0.1 - #36
Merged
Merged
Conversation
Bumps [@eslint/js](https://github.com/eslint/eslint/tree/HEAD/packages/js) from 9.39.4 to 10.0.1. - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](https://github.com/eslint/eslint/commits/v10.0.1/packages/js) --- updated-dependencies: - dependency-name: "@eslint/js" dependency-version: 10.0.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
This was referenced Apr 26, 2026
schmug
added a commit
that referenced
this pull request
Apr 26, 2026
schmug
added a commit
that referenced
this pull request
Apr 26, 2026
Without an explicit pin, setup-node v6 reading engines.node (>=22.12.0) from package.json picks the latest installed match, which on the GH Actions runners is currently Node 24.14.1. Node 24 ships npm 11 which has more permissive peer-dep handling on `npm ci` than the npm 10.9.2 that ships with Node 22 — the version Cloudflare Pages uses. Result: CI was green on a lockfile that CF Pages strict-rejected, which is what let the @eslint/js v9->v10 bump (#36) merge to main and break six consecutive prod deploys. Pinning to 22 via .nvmrc aligns CI with CF (CF Pages also reads .nvmrc) so install-time peer conflicts surface in PR CI instead of only failing prod. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
schmug
added a commit
that referenced
this pull request
Apr 26, 2026
Without an explicit pin, setup-node v6 reading engines.node (>=22.12.0) from package.json picks the latest installed match, which on the GH Actions runners is currently Node 24.14.1. Node 24 ships npm 11 which has more permissive peer-dep handling on `npm ci` than the npm 10.9.2 that ships with Node 22 — the version Cloudflare Pages uses. Result: CI was green on a lockfile that CF Pages strict-rejected, which is what let the @eslint/js v9->v10 bump (#36) merge to main and break six consecutive prod deploys. Pinning to 22 via .nvmrc aligns CI with CF (CF Pages also reads .nvmrc) so install-time peer conflicts surface in PR CI instead of only failing prod. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Bumps @eslint/js from 9.39.4 to 10.0.1.
Release notes
Sourced from
@eslint/js's releases.... (truncated)
Commits
84fb885chore: package.json update for@eslint/jsrelease1f66734chore: addeslinttopeerDependenciesof@eslint/js(#20467)f3fbc2fchore: set@eslint/jsversion to 10.0.0 to skip releasing it (#20466)b4b3127chore: package.json update for@eslint/jsrelease0b14059chore: package.json update for@eslint/jsreleasefa31a60feat!: addnameto configs (#20015)1e2cad5chore: package.json update for@eslint/jsrelease454a292feat!: updateeslint:recommendedconfiguration (#20210)c6358c3feat!: Require Node.js^20.19.0 || ^22.13.0 || >=24(#20160)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)