feat(ci): add canary release workflow for linux and macos#80
Open
swarit-stepsecurity wants to merge 1 commit into
Open
feat(ci): add canary release workflow for linux and macos#80swarit-stepsecurity wants to merge 1 commit into
swarit-stepsecurity wants to merge 1 commit into
Conversation
Internal pre-release builds gated by the `canary-release` GitHub environment. Builds run on native runners (ubuntu + macos), macOS binary is ad-hoc signed, all artifacts get Sigstore cosign + SLSA attestation. Lightweight `canary-<run>-<sha>` tag keeps these out of the semver tag pool. Production release path is untouched.
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
1 participant
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.
Internal pre-release builds gated by the
canary-releaseGitHub environment. Builds run on native runners (ubuntu + macos), macOS binary is ad-hoc signed, all artifacts get Sigstore cosign + SLSA attestation. Lightweightcanary-<run>-<sha>tag keeps these out of the semver tag pool. Production release path is untouched.What does this PR do?
Type of change
Testing
./stepsecurity-dev-machine-guard --verbose./stepsecurity-dev-machine-guard --json | python3 -m json.toolmake lintmake testRelated Issues