ci: bump autorest.powershell submodule for CFSClean pnpm-lock v9 fix - #3731
Merged
Ramses Sanchez-Hernandez (ramsessanchez) merged 1 commit intoAug 19, 2026
Conversation
Advance the autorest.powershell submodule c42e7f8e -> b1669283 to pick up powershell-v2 PRs #21 and #22: - #21 regenerates common/config/rush/pnpm-lock.yaml to lockfileVersion 9 (matching the pinned pnpm 10.34.4), so the Rush Build step runs a frozen, deterministic `rush install` instead of ignoring the incompatible v6 lockfile and re-resolving/re-fetching from public npm. This eliminates the residual 2x registry.npmjs.org egress that kept PermissiveCFSClean = False on pipelines 187 / 221 / 663. - #22 bumps js-yaml 3.15.0 -> 3.15.1. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6ea00b50-c719-469b-bf9c-72120184bfe0
Ramses Sanchez-Hernandez (ramsessanchez)
approved these changes
Aug 19, 2026
Ramses Sanchez-Hernandez (ramsessanchez)
merged commit Aug 19, 2026
65532f3
into
main
6 of 8 checks passed
Ramses Sanchez-Hernandez (ramsessanchez)
deleted the
gavinbarron/bump-autorest-pnpm-lockfile
branch
August 19, 2026 19:32
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
2 participants
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
Advance the
autorest.powershellsubmodulec42e7f8e→b1669283(powershell-v2 tip), picking up:common/config/rush/pnpm-lock.yamlto lockfileVersion 9 (matching pinned pnpm 10.34.4)$prefix to all OData query options. #22 — bumpjs-yaml3.15.0→3.15.1Why (CFSClean / 1ES network isolation)
Pipelines 187 / 221 / 663 kept leaking a stable 2×
registry.npmjs.orgper generation job (PermissiveCFSClean = False). Root cause: the committed Rush lockfile waslockfileVersion 6.0whilerush.jsonpins pnpm 10.34.4 (v9), so pnpm logged "Ignoring not compatible lockfile" and re-resolved + re-fetched every run — following the feed's upstreamdist.tarballto public npm on first-request cache misses. Neither#3718(npm_config_registry) nor#3729(.pnpmfile.cjsafterAllResolvedrewrite) could fix it while the lockfile was ignored.The submodule fix regenerates the lockfile to v9 so
rush installruns frozen and deterministic, resolving every tarball through the authenticated private feed. Verified locally: 0registry.npmjs.orgURLs in the lockfile; frozen install reports "Already up to date."Validation after merge
Once merged, the first
individualCIrun of def 187 should reportregistry.npmjs.org = 0(the strictCFSCleantier). The PowerShell Gallery (CFSClean2) egress is handled separately by draft PR #3720;PermissiveCFSCleanflips True once both land.