fix: fix release workflow permissions for devcontainers tagging - #7
Merged
Conversation
devcontainers/action creates the `feature_<id>_<version>` tag through the git refs API using GITHUB_TOKEN. With `contents: read` the call is rejected and the action downgrades the failure to a warning, so releases succeeded while silently skipping every tag. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017wvd5GPvBZVEU8QgkPkNQb
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017wvd5GPvBZVEU8QgkPkNQb
nozaq
changed the title
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.
Summary
Update the release workflow to grant
writepermissions for repository contents, allowing the devcontainers action to properly tag released commits.Changes
contentspermission fromreadtowritein the release workflowfeature_<id>_<version>) via the GitHub APIDetails
The devcontainers/action requires write access to repository contents to tag the released commit through the git refs API. Without this permission, the action would log a "Failed to automatically add repo tag" warning but continue execution, leaving releases untagged.
https://claude.ai/code/session_017wvd5GPvBZVEU8QgkPkNQb