Repository navigation
docs: reconcile stable recovery and beta release guidance - #322
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.
Reconciles the stable startup hotfix's public recovery guidance and Zed release references into dev while preserving the beta feature line. The changelog distinguishes stable 0.1.44 from beta.2 and explains the incompatible-downgrade restriction.
Startup, authentication and PowerShell corrections already exist in dev. Stable's narrow recorded-schema guard remains on main because beta already performs the broader compatibility/backup/writer checks; its narrower implementation is not substituted into beta. No runtime or migration behavior changes in this PR.
Validation: documentation and release references checked against the main hotfix and beta.2; whitespace validation passed. Stable publication is being verified independently through the release workflow and isolated artifact installation/TUI acceptance.