Repository navigation
feat(ci): gate releases on protected storage acceptance - #11
Merged
Merged
Conversation
AndresRCB
marked this pull request as ready for review
October 12, 2026 13:04
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 release-please PR management using the built-in GitHub token, with explicit CI and protected storage acceptance for each recorded release candidate. Publication requires matching source evidence, successful validation, and current human approval before publishing archives, Debian packages, and container images.
CI builds the pinned test storage server from upstream source and installs pinned Semgrep directly, avoiding Docker Hub pull quotas.
Automation remains disabled until the documented branch, human Code Owner, environment, and storage federation settings are configured. GitHub dispatch and OIDC activation still require protected workflow validation.
Validation: 48 Python regressions, workflow lint, repository Go checks with native Semgrep, the full race suite against the pinned local storage server, and local binary build/version validation passed. Local live storage acceptance and scoped recovery passed; release archives, packages, checksums, and container binaries were validated.