Repository navigation
ci: pin npm to 11.5.1 in the publish workflow - #19
Merged
Merged
Conversation
npm@latest is now npm 12, which requires Node ^22.22.2, ^24.15.0 or >=26, while .nvmrc pins Node 24.11, so the Update npm CLI step failed with EBADENGINE before anything was published. 11.5.1 is the first npm with OIDC trusted publishing and supports Node 24.11; agentfront/frontmcp pins the same version.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Contributor
Cherry-pick CreatedA cherry-pick PR to Please review and merge if this change should also be in If the cherry-pick is not needed, close the PR. |
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
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.
The Publish Release run for 2.3.3 (https://github.com/agentfront/vectoriadb/actions/runs/37323445753) failed at Update npm CLI for trusted publishing:
The step installed
npm@latest, which is now npm 12. That release requires a newer Node than thev24.11that.nvmrcpins. The run stopped before Compute version, so it bumped nothing and published nothing.This pins
npm@11.5.1, the first npm with OIDC trusted publishing. Itsenginesfield accepts Node 24.11, and agentfront/frontmcp's publish workflow pins the same version. Once this merges, rerun Publish Release onrelease/2.3.xto publish 2.3.3 with the worker-entry fix (#17).