Skip to content

ci: repin ci-workflows to v0.36.0 - #82

Merged
kyle-sexton merged 1 commit into
mainfrom
ci/repin-ci-workflows-v0.36.0
Oct 4, 2026
Merged

kyle-sexton merged 1 commit into
mainfrom
ci/repin-ci-workflows-v0.36.0

Conversation

@kyle-sexton

Copy link
Copy Markdown
Member

No related issue: Phase 8 step 3 of the org GitHub Actions conventions migration (one ci-workflows version everywhere).

Summary

Repins this repository's repo-owned ci-workflows references to v0.36.0 (fb56986), so every repo converges on one ci-workflows release. Sync-managed callers move separately through the standards repin and sync.

Fix

Repo-owned uses: melodic-software/ci-workflows/... pins move from v0.34.0 (7446b51) or v0.35.0 (69e506b) to fb56986808750d6856c27de78df15e150027b8dc # v0.36.0. Composite paths moved since v0.34.0 are mapped (comment-hygiene to check-comment-markers, machine-specific-paths to check-machine-paths) where pinned.

Verification

Related

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 4, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-04T22:16:58.800298Z b70b59a PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@claude

claude Bot commented Oct 4, 2026 •

Copy link
Copy Markdown

Claude finished @kyle-sexton's task in 1m 35s —— View job


Code review: ci: repin ci-workflows to v0.36.0

  • Gather context (PR diff, CLAUDE.md/AGENTS.md)
  • Review changed workflow files for correctness
  • Verify version pins / SHA-version comment pairing
  • Verify composite path remaps mentioned in PR body
  • Post findings

No findings. This is a clean, mechanical pin bump with no logic changes:

  • Both changed files (pr-automerge-dependabot.yml, pr-require-checks.yml) are confirmed repo-owned callers (no SYNC-MANAGED FILE banner), matching the PR body's claim that sync-managed callers move separately.
  • All four touched pins now resolve to the same 40-character SHA fb56986808750d6856c27de78df15e150027b8dc, each correctly paired with the # v0.36.0 comment — internally consistent, and the short SHA in the PR body (fb56986) matches.
  • Checked the rest of the repo for other repo-owned ci-workflows pins that might have been missed: pr-check-managed-files-hosted.yml, pr-review-security-hosted.yml, and pr-review-hosted.yml still pin v0.34.0, but all three carry the SYNC-MANAGED FILE banner (source of truth in melodic-software/standards), so correctly out of scope for this PR per its stated scope.
  • The PR body's note about composite-path remaps (comment-hygiene→check-comment-markers, machine-specific-paths→check-machine-paths) doesn't apply to either changed file — neither path appears here, consistent with the body's "where pinned" qualifier.
  • Diff is a pure version/SHA swap; no with: inputs, permissions, triggers, or step ordering changed.

Not independently verified (author-claimed in the PR body, not re-run here):

  • That every pinned path exists at fb56986 in ci-workflows.
  • actionlint results — the binary is not installed in this sandbox (which actionlint failed) and the repo's own .cursor/install.sh was not run, so I could not execute it myself.
  • The runner-policy contract claims tied to melodic-software/standards#697.

No REVIEW.md-flagged concerns apply: this isn't a port (no reshape/drop decisions to record) and doesn't add MCP servers or hooks (no trust review needed).

@claude

claude Bot commented Oct 4, 2026 •

Copy link
Copy Markdown

Claude finished @kyle-sexton's task in 6m 21s —— View job


Security review — skipped

  • Gather context (PR diff, changed files)
  • Apply skip gate
  • Review changed workflow files for security-relevant surface
  • Report findings

Result: no security review needed. This PR only repins existing uses: SHA references in two workflow files (.github/workflows/pr-automerge-dependabot.yml, .github/workflows/pr-require-checks.yml) from v0.34.0/v0.35.0 commit SHAs to the v0.36.0 commit SHA (fb56986808750d6856c27de78df15e150027b8dc), each still accompanied by its # vX.Y.Z comment. No trigger changes, no permissions: changes, no new inputs/secrets, no logic changes, and all pins remain full-length commit SHAs (no loosening to a tag/branch). This matches the skip gate: "Change has no security-relevant surface after reading the diff."

No CLAUDE.md/AGENTS.md/rules-file/skill changes are present in this diff, so the instruction-surface-deletion check does not apply either.

Per this lane's scope, supply-chain pin changes are zizmor's advisory lane, not this lane's — and in any case these pins are only being bumped forward to a newer SHA, not loosened.

No findings to report.

@kyle-sexton
kyle-sexton enabled auto-merge (squash) October 4, 2026 22:15
@kyle-sexton
kyle-sexton merged commit 24d2158 into main Oct 4, 2026
11 checks passed
@kyle-sexton
kyle-sexton deleted the ci/repin-ci-workflows-v0.36.0 branch October 4, 2026 22:16
@github-actions

github-actions Bot commented Oct 4, 2026

Copy link
Copy Markdown

claude-review has reviewed this pull request through b70b59a; a later push is reviewed from there.

@github-actions

github-actions Bot commented Oct 4, 2026

Copy link
Copy Markdown

claude-security-review has reviewed this pull request through b70b59a; a later push is reviewed from there.

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