chore(release): prepare 1.0.0-beta Latest and isolate legacy updates - #2947
Merged
Merged
Conversation
wgqqqqq
marked this pull request as ready for review
September 10, 2026 12:42
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.
Prepare the public
1.0.0-betarelease (tagv1.0.0-beta, with no numbered suffix). The stable channel explicitly publishes it as a non-prerelease GitHub Latest release. Desktop, CLI, and SSH installation use versioned update feeds; legacy Desktop and CLI feeds retain the unchanged v0.2.19 manifests so installed 0.2.x clients are not offered 1.x updates.Keep this PR in draft until release time. Merging the package version change into main automatically dispatches Desktop Package with
release_channel=stableandupload_to_release=true; successful packaging publishes the release. Update the production mirror script before release and verify both legacy and 1.x feeds afterwards. Existing numbered 1.0.0-beta.N installations require manual installation because SemVer orders the unnumbered beta below them.Validation: release version consistency, GitHub configuration checks, release packaging tests, focused manifest/channel/mirror tests, Rust formatting, and git diff whitespace checks passed. Public GitHub and mirror legacy manifests were read and confirmed as 0.2.19. One existing platform-specific workflow test was skipped. No native packages were built or published, and remote workspace, remote control, Peer Device Mode, and Detached Dispatch were not exercised end to end; SSH feed selection is covered by a local contract test.