Repository navigation
fix(ci): use Node and pnpm certificate validation releases - #81
Merged
Merged
Conversation
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.
What Problem This Solves
RTT workflows select Node and native pnpm releases that can accept the compromised eMudhra keys.
User Impact
Select the qualified fixed Node patch within each existing major and native pnpm12.15.0 across the eight package-manager workflow owners. Keep the owning workflow contract test consistent.
Why This Change Was Made
Node and native pnpm12 have independent certificate verifiers, so update both existing owners. Preserve live-run triggers, credentials, channel policies and release gates.
Evidence
All232 offline tests, dataset validation, README regeneration comparison, workflow actionlint and git diff --check pass in the isolated Linux arm64 worker. The actual unmodified pinned pnpm/setup@v3.1.1 action with native pnpm12.15.0 and runtime node@26.12.1 succeeds; the installed runtime binary exactly matches the qualified official Node SHA256. This channel uses pnpm runtime distribution resolution, rather than the unavailable npm node wrapper release. Independent P2 review is clean. Actual qualified Node and native pnpm releases reject the incident chains, including explicit old CA inputs, with positive controls.
Credentialed RTT/channel runs were not dispatched. Existing installed runtimes, provider-owned runner/action runtimes and native platform coverage remain separate obligations. This PR does not run live campaigns or publish releases.
The8measurement workflows also use the supported nativepnpm12 setting
pnpm_config_pm_on_fail=ignoreso their chosen12.15.0 runtime stays authoritative when entering historical release andQA checkouts. The removedMANAGE_PACKAGE_MANAGER_VERSIONSsetting was ineffective inpnpm12. Actual projects declaring12.5.1 and12.15.0 both retained12.15.0 through version, store and real dependency-install commands. All232tests,8parsed workflow environments, actionlint with the repository’s existing configuration, and fresh full-contextP2review passed. No live channel scenario or result publication was run.