Fix published release smoke lifecycle (BEAR-104) - #103
Merged
Conversation
Model the persistent home, migration controller, and migrated target as distinct identities in the public release smoke. Prove migration completion and ready status before uninstalling, and document the v2.1.2 fix-forward release.
![mobilyze-open-swe-studio2[bot]](https://avatars.githubusercontent.com/in/4340220?s=60&v=4){kind=small}
Contributor
Merge Queue Status
This pull request spent 7 seconds in the queue, including 1 second running CI. Required conditions to merge
|
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.
Summary
v2.1.2releaseWhy
The immutable
v2.1.1release published successfully, but its public smoke failed because the tagged harness omitted the required first-install control task. The first local correction then proved the harness also made its sole migration target the persistent home, which the lifecycle intentionally excludes from inventory. Product behavior failed closed correctly; the smoke fixture was modeling the lifecycle incorrectly.v2.1.1remains immutable. This PR is the smallest fix-forward recovery approved twice by Fable.Verification
scripts/release-smoke.sh v2.1.1passes against the live installer and published releasego test ./...go test -race ./...go vet ./...gofmt -l .cleangit diff --checksh -n install.shsh -n scripts/release-smoke.shv2.1.2cross-buildsBEAR-104 remains open until the Mergify merge, immutable
v2.1.2tag, public CI/publish/smoke, official reinstall, genuine Codex restart, and rendered direct/delegated canaries all pass.Refs BEAR-104