chore(release): add two-phase release workflows [PSEC-656]#73
Merged
stevebeattie merged 1 commit intochainguard-dev:mainfrom Apr 2, 2026
Merged
Conversation
Adds prepare-release and create-release GitHub Actions workflows, along with octo-sts identity files for both. The release process needs the XCCDF Benchmark version element in the SCAP datastream to reflect the release tag, but branch protection on main prevents a tag-then-patch approach. Patching first and tagging the resulting merge commit ensures the tag always points to a commit with the correct version, keeping releases immutable. Notes: full datastream validation (validate_xml) is stubbed out in create-release as it is currently failing; it and future per-rule evaluation steps can be re-enabled in that job once ready. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
egibs
approved these changes
Apr 2, 2026
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.
Adds prepare-release and create-release GitHub Actions workflows, along with octo-sts identity files for both.
The release process needs the XCCDF Benchmark version element in the SCAP datastream to reflect the release tag, but branch protection on main prevents a tag-then-patch approach. Patching first and tagging the resulting merge commit ensures the tag always points to a commit with the correct version, keeping releases immutable.
Notes: full datastream validation (validate_xml) is stubbed out in create-release as it is currently failing; it and future per-rule evaluation steps can be re-enabled in that job once ready.