Skip to content

Pin Release workflow actions to commit SHAs - #10

Merged
MrPippi merged 1 commit into
mainfrom
cc/charming-keller-a0vyen
Oct 9, 2026
Merged

MrPippi merged 1 commit into
mainfrom
cc/charming-keller-a0vyen

Conversation

@MrPippi

@MrPippi MrPippi commented Oct 9, 2026 •

Copy link
Copy Markdown
Owner

Summary

The Release workflow runs with contents: write: it creates tags and publishes releases. It should therefore run third-party code fixed to a commit instead of following a tag that can be moved.

Action Before After
actions/checkout @v7 @3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
actions/setup-java @v6 @de7274f081f381c8f8158605e0321c36c376e2e6 # v6.0.1
  • I resolved the SHAs with git ls-remote --tags against the upstream repos. Both tags are lightweight, so these are the commit IDs.
  • v7 and v7.0.1 currently point to the same commit, and so do v6 and v6.0.1, so behaviour is unchanged.
  • The trailing # vX.Y.Z comment records the version. A header comment in the workflow asks that the SHA and the comment be updated together.
  • CHANGELOG.md has an [Unreleased] entry for this.

build.yml is left on tags. It has only default read permissions and doesn't publish anything.

Test plan

  • YAML parses; only the two uses: lines and a comment changed
  • Build CI is green. This PR doesn't run release.yml; the next release run will exercise the pinned actions.

🤖 Generated with Claude Code

https://claude.ai/code/session_018syaxkhsW9ioZChSmth9Xx


Generated by Claude Code

actions/checkout v7.0.1 (3d3c42e) and actions/setup-java v6.0.1
(de7274f), the same commits the v7/v6 tags point to today, so behaviour
is unchanged. The release job has contents: write, so it should not
follow a mutable tag.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018syaxkhsW9ioZChSmth9Xx
@MrPippi
MrPippi marked this pull request as ready for review October 9, 2026 02:41
@MrPippi
MrPippi merged commit 54e478c into main Oct 9, 2026
1 check passed
@MrPippi MrPippi mentioned this pull request Oct 9, 2026
2 tasks done
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.

2 participants