Repository navigation
Add a release workflow that builds the scanner once for the appsec scan - #18
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Adds
.github/workflows/versprite-scanner-release.yml, run by hand with a full commit SHA. It builds Linux amd64 and arm64 scanners for that commit and attaches them, withSHA256SUMS, to ascanner-<first 12 of SHA>release.The appsec-workflows secret scan downloads these and checks them against checksums pinned in its own repo, instead of every repo building the scanner itself (about 5 minutes per repo per version).
v, so upstream'srelease.yml(goreleaser, DockerHub) never runs for it.