PFM-ISSUE-34453 - github-actions: correct the node-version claim (most branches are on npm 11) - #175
Open
Kaltenbach wants to merge 1 commit into
Open
Conversation
…st branches are on npm 11
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.
Replication of #171 to
release/26.2, sothe tooling stays byte-identical across all seven branches.
Documentation only — two files, both comment/message text:
warn-foreign-registry.sh(the advisory's jobsummary) and
README.md. No predicate, exit code or control flow changed.#164 claimed "runners pinned to node 18.19.1 are on npm 10" and "nothing fails in CI today". Read from the
workflow files, only
release/25.2pins node 18.19.1;release/25.3and every newer branch — including thisone — pin node 22.15.0, which is npm 11, the version that drops the registry's path prefix. Un-normalized lockfiles
on those branches were failing;
cplace-vwg-ptm-ferun 31167462200 is the report.
Both files now carry a per-branch table instead of a single sentence. The substantive discussion is on #171.