Skip to content

fix(ci): correct pnpm action version comments - #603

Closed
Lutar, Stephen P. (stephenlutar2-hash) wants to merge 1 commit into
mainfrom
agent/fix-pnpm-action-version-comments
Closed

fix(ci): correct pnpm action version comments#603
Lutar, Stephen P. (stephenlutar2-hash) wants to merge 1 commit into
mainfrom
agent/fix-pnpm-action-version-comments

Conversation

@stephenlutar2-hash

Copy link
Copy Markdown
Member

Summary

Correct stale # v4 comments left after #583 pinned pnpm/action-setup
to the immutable v6.0.10 commit.

Scope

  • 16 workflow files
  • 20 comment-only replacements
  • no action ref, trigger, permission, input, command, or lockfile changes

Proof

  • git diff --check: pass
  • parsed YAML semantic identity: 16/16 workflows
  • executable ref comparison: 20/20 byte-identical
  • upstream tag peel: v6.0.10^{} = 0977fd99725f1db4007ccb2928dbb4e90d06cc86
  • action-pin inventory: zero violations
  • Gitleaks 8.21.2: no unallowlisted findings across 5,315 commits
  • project secret scanner: clean; 15/15 tests passed
  • local typecheck: inconclusive after a 10-minute timeout

Merge gate

Require a valid signature and DCO, terminal exact-head hosted checks, resolved
threads, and a normal protected merge. The hosted exact-head Typecheck is
authoritative for this PR.

Workcell: PR-583-comment-correction

Related: #583

Align all 20 workflow comments with the immutable pnpm/action-setup v6.0.10 commit.
Executable refs and parsed workflow semantics are unchanged.

Verification:
- git diff --check
- parsed YAML semantic identity across 16 workflows
- exact action refs unchanged and SHA-pinned
- Gitleaks 8.21.2: no unallowlisted findings across 5,315 commits
- project scanner: clean; 15 tests passed
- local typecheck: inconclusive after a 10-minute timeout

Workcell: PR-583-comment-correction
Signed-off-by: SZL Codex <codex-bot@szl-holdings.example>

Copy link
Copy Markdown
Member Author

Superseded by clean signed successor #604.

The #603 tree and scope were correct, but GitHub reported its exact head
2decc18ff3fedef9a1de48cbdcfce6f5e87d4a7b as
verified=false, reason=no_user because the synthetic author email did
not map to a GitHub user. No force-push or history rewrite was used.

#604 carries the byte-identical tree at exact head
81bcc5ce57d63f6d888d4ca0045cb358532a1865, which GitHub reports as
verified=true, reason=valid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant