chore: stage v0.7.0-rc.1 - #98
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
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.
Why\n\nCloud production depends on management routes added after v0.6.0, including GET /events and POST /sequences/preflight. Fresh managed instances are pinned to v0.6.0, so Cloud reports them as degraded.\n\n## Change\n\n- stage the already-green 0.7.0-dev workspace as 0.7.0-rc.1\n- smoke-test the exact Cloud management routes in CI and each pushed architecture image\n- ensure prerelease tags do not move GHCR latest or GitHub Releases latest\n- skip install.sh latest-release smoke for prereleases\n\n## Validation\n\n- cargo metadata --locked --no-deps --format-version 1\n- ./scripts/test-review-fix-guards.sh\n- actionlint .github/workflows/ci.yml .github/workflows/release.yml\n- cargo fmt --all -- --check\n- git diff --check\n\nAfter merge and green main CI, tag v0.7.0-rc.1, publish the image, canary it on one disposable Cloud instance, then promote only after the production lifecycle passes.