Repository navigation
feat: permanently allocate trusted release runs and retry attempts - #10
Merged
Merged
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
What changes
Make the existing bounded release pool permanent across current and future Platform run IDs and retry attempts. The protected GitHub credential stays on the Gateway; the host gets only a scoped one-job JIT configuration. Keep the existing pinned-image/nonroot/fresh-workspace lifecycle and independent offline cleanup.
Verification
101 tests pass, one opt-in Docker-runtime test skipped. Full source-image contract already passes against the actual immutable production image. Live plan discovered beta7 attempt2 Kotlin job109459417028 without any run-specific allowlist. Production activation and one-job lifecycle are being verified and recorded in the operator's private evidence; this does not alter release tags, publish packages manually, or touch contributor PR branches.
The Docker application-image cargo-binstall repair is separate: dashpay/platform#5203.
Prepared by infraclaw using the user-authorized internal-branch/PAT route; account attribution is not a personal approval.