Skip to content

Release GSwitch 1.0.26 - #184

Merged
squarepots merged 1 commit into
mainfrom
release-1.0.26
Oct 16, 2026
Merged

squarepots merged 1 commit into
mainfrom
release-1.0.26

Conversation

@squarepots

Copy link
Copy Markdown
Member

What changed

Release GSwitch 1.0.26 by synchronizing the Tauri, JavaScript, Cargo package, and Cargo lock versions. The diff changes only the four version fields.

The release ships these merged changes on main at 1859bbc:

The 1.0.25 release draft was never published, so 1.0.24 users also receive #179 (0174e1f): Update in the Codex CLI dialog waits for GSwitch's own work instead of reporting that another operation is in progress.

Why

Refresh all was slow, and Wake failed as busy while a refresh ran.

Validation

  • pnpm run version:sync, pnpm run version:check, and git diff --check passed locally.
  • main at 1859bbc passed CI, including CI gate and all three CodeQL analyses. Locally on Windows at that commit: cargo test (181 passed, 1 ignored), vitest run (158 passed), and tsc --noEmit.

Real-account acceptance

This release changes quota and Wake, so docs/release.md calls for real-account acceptance. The maintainer waived it for this release, at main commit 1859bbc; no preview was built. Refresh speed with real accounts, and Wake during Refresh all or with an expired saved token, are not claimed as validated.

Remaining

After merge: tag the exact merged main commit as v1.0.26, run the release workflow, inspect the draft assets and notes, and publish. The unpublished 1.0.25 draft is left unchanged.

Synchronize the Tauri, JavaScript, Cargo package, and Cargo lock versions.
@squarepots
squarepots enabled auto-merge (squash) October 16, 2026 10:28
@squarepots
squarepots merged commit 0dd0b7f into main Oct 16, 2026
12 checks passed
@squarepots
squarepots deleted the release-1.0.26 branch October 16, 2026 10:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant