feat: add transactional upgrade rollback - #54
Merged
Conversation
Owner
Author
|
Merged using rebase. What changed after review:
Verification:
Landed on
Thanks @shakkernerd! |
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.
Summary
ocm upgrade rollbackfor explicit, transactional restoration of the runtime, environment snapshot, binding, and managed service state captured before an upgradeVerification
cbx_a55a7013c2d7:cargo test --lockedcbx_a55a7013c2d7:cargo check --locked --all-targetscbx_a55a7013c2d7:cargo check --locked --target x86_64-pc-windows-gnu2026.6.11,2026.6.33,2026.7.1,2026.7.1-2,2026.7.2-beta.3, and frozen sourceec8f957freporting2026.7.22026.7.2to2026.7.2-beta.3runtime-only downgrade rejected before state, snapshot, or history mutationFollow-up
Separate compatibility-hardening PRs will extend the general environment operation lock across the complete normal-upgrade path and make failed-rollback audit-record cleanup resilient if history persistence itself fails. The explicit rollback path in this PR already holds its operation lock for the full rollback and restores state before recording a rollback failure.