Repository navigation
Reject unsupported success receipts and harden review and process lifecycles - #1
Merged
Merged
Conversation
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
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.
A status request could accept historical success during another operation, signed reviews could be replaced by unsigned approval/import, and successful receipt metadata could disagree with the retained logs. Status now holds the project lock, supports cancellation, reassesses named-test/package completion, verifier summaries and targeted mutant diagnostics, and rechecks authorization. Signed state cannot be silently downgraded.
Check descendants are now cleaned up even when their parent exits first. Windows starts the root suspended and assigns it to a kill-on-close Job Object before running it; unavailable containment fails closed. Native regression tests cover inherited pipes and detached children.
The CLI reports its tagged module version when installed with
go install. Release instructions and the changelog describe the v0.2.1 integrity fixes. CI action revisions are pinned by commit, and the independent signed gate advances only to the already-qualified v0.2.0 tooling.Validation: local regression/race/vet checks and Go 1.20 compatibility pass; real pinned-Gobra integrations pass. Required PR checks run the final code on Linux, macOS and Windows, plus real verifier and signed CI workflows. Release artifacts will be built twice, compared and smoke-tested from a clean checkout before publishing.