Repository navigation
Release GSwitch 1.0.25 - #180
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
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.
What changed
Release GSwitch 1.0.25 by synchronizing the Tauri, JavaScript, Cargo package, and Cargo lock versions. The product change, #179, merged as
0174e1f8.Why
Ship the fix that lets Update in the Codex CLI dialog wait for GSwitch's own quota refresh instead of reporting "Another GSwitch operation is in progress".
Validation
pnpm run version:sync,pnpm run version:check, andgit diff --checkpassed locally; the diff changes only the four version fields.Remaining
Real-account acceptance under
docs/release.mdcovers sign-in, switching, quota, Wake, credential storage, and recovery. This release changes only the Codex CLI update path, so that gate does not apply and those flows are not claimed as validated. After merge: tag the exact mergedmaincommit, run the release workflow, inspect the draft assets and notes, and publish.