chore(ui): pin packageManager to npm@11.6.2#2245
Draft
cjlg-soloio wants to merge 2 commits into
Draft
Conversation
Node 24.13.0 (ui/.nvmrc) bundles npm 11.6.2. Pinning packageManager keeps npm installs reproducible and prevents package-lock.json metadata churn across npm versions. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Carlos Logroño Guerrero <carlos.logrono@solo.io>
Regenerated with the pinned npm (11.6.2) so the lockfile matches the packageManager field. Diff is metadata-only (peer/optional flags); no dependency version changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Carlos Logroño Guerrero <carlos.logrono@solo.io>
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.
Description
🤖 written by Claude (start)
Follow-up to a review comment on #2180: pins the npm version via the
packageManagerfield sonpm installis reproducible andui/package-lock.jsonstops picking up metadata churn across npm versions.ui/.nvmrcpins Node 24.13.0, which bundles npm 11.6.2 — so the field is set tonpm@11.6.2, consistent with the Node version CI already reads from.nvmrc.Files
Modified
ui/package.json— adds top-level"packageManager": "npm@11.6.2"ui/package-lock.json— regenerated under npm 11.6.2 to match the pin; metadata-only diff (peer/optionalflags), no dependency version changesTesting
Change type
chore / cleanup — dev tooling only. No product or runtime code changed.
Changelog
NONE🤖 written by Claude (end)