feat(ci): add tracked staging validation - #181
Open
rishibalakrishnan wants to merge 3 commits into
Open
Conversation
|
Updated description for acceptance criteria input.
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 portable GitHub deployment records and exact live release identity verification for manually dispatched client staging builds. Staging requests remain explicit and serialized; metadata contains the PR, SHA, TTL, acceptance criteria, rollback image, and image digest without BB-local identifiers.
Verification:
go test ./cmd/bskyweb/_releasepreview (registered in BB after PR creation)