Repository navigation
Pin Release workflow actions to commit SHAs - #10
Merged
Merged
Conversation
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
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.
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.actions/checkout@v7@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1actions/setup-java@v6@de7274f081f381c8f8158605e0321c36c376e2e6 # v6.0.1git ls-remote --tagsagainst the upstream repos. Both tags are lightweight, so these are the commit IDs.v7andv7.0.1currently point to the same commit, and so dov6andv6.0.1, so behaviour is unchanged.# vX.Y.Zcomment records the version. A header comment in the workflow asks that the SHA and the comment be updated together.CHANGELOG.mdhas an[Unreleased]entry for this.build.ymlis left on tags. It has only default read permissions and doesn't publish anything.Test plan
uses:lines and a comment changedrelease.yml; the next release run will exercise the pinned actions.🤖 Generated with Claude Code
https://claude.ai/code/session_018syaxkhsW9ioZChSmth9Xx
Generated by Claude Code