Conversation
…improvement Harden Docker Sandboxes lifecycle recovery
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.
Release intent
Merge the validated
developbranch intomainas the source commit for the plannedv0.3.2source-only release. This PR does not create the tag or GitHub Release.Included changes
Validation
488d52a242199b090dfbacb6bc237e7b96c0bb18passed Host trust verification and Core runner verification.git diff --check origin/main...origin/developpassed locally after refreshing and fast-forwarding the localdevelopbranch.v0.3.2commit again before publishing.After merge
Create and push annotated tag
v0.3.2at the resultingmaincommit, then manually dispatch the source-only Release workflow with the exact confirmationpublish source-only release. Tagging and release publication remain separate approval steps.