Prepare stable v1.1.0 and simplify V2 onboarding - #91
Merged
Merged
Conversation
Lash-L
marked this pull request as ready for review
September 18, 2026 17:55
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.
Prepare
1.1.0as the stable release of the V2 recovery and multipart NC changes. Remove the obsolete V2 unsupported status so guided pairing progresses through key recovery and completes after MQTT connects.Remove the separate V2 research page and duplicate Beta testing instructions. V2 uses the normal onboarding flow; keep one practical note about recovery time and the sample counter. Update the confirmed-vacuum list and stable package/add-on versions. Retain Beta at
1.1.0-rc2, mark it currently unused, and document switching to stable without implying that add-on data transfers automatically.Validation:
After merge, publish a non-prerelease
v1.1.0release to build the stable container image and aliases. The release has not been published.