Prepare Hub 0.20.3, desktop 0.6.3 and mobile 0.6.5 releases - #445
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.
Prepare Hub/CLI/node 0.20.3, desktop 0.6.3, and Android/iOS 0.6.5 from main after #444. Update the Hub workspace and lockfiles, set the desktop installer version, and document the release scope, physical RC acceptance and final distribution checks. Mobile marketing versions remain tag-driven.
The internal iOS 0.6.5 candidate has already used CFBundleVersion 0.6.5. Generate an independent numeric build number from the workflow run and retry so the final 0.6.5 upload does not reuse that identifier.
Validation: locked offline Cargo metadata for both workspaces, workflow YAML parsing, execution of the iOS version step for new runs/retries and invalid bounds, and git diff --check. Runtime behavior is unchanged from #444, whose five CI checks passed. Final signed artifacts still require distribution checks; no release tags or public releases are created by this PR. #144 and #406 remain excluded.