Skip to content

chore: bump version to 0.6.8-rc.3 - #75

Merged
Nic-dorman merged 1 commit into
mainfrom
chore/bump-0.6.8-rc.3
May 1, 2026
Merged

chore: bump version to 0.6.8-rc.3#75
Nic-dorman merged 1 commit into
mainfrom
chore/bump-0.6.8-rc.3

Conversation

@Nic-dorman

Copy link
Copy Markdown
Contributor

Third internal-tester pre-release.

Adds on top of rc.2

Headline test for rc.3

Anyone on installed v0.6.8-rc.1 or rc.2 (Linux/macOS) with Pre-release builds toggled on should:

  • Auto-detect rc.3 with the new teal update banner in the sidebar
  • Click → dialog with teal Pre-release badge
  • Click Update & Restart → download, install, app actually restarts cleanly into rc.3 (Linux/macOS — was broken on rc.1, fixed in fix(updater): restart on Linux/macOS after install #73)
  • Sidebar shows the teal PRE-RELEASE badge once running on rc.3

Release process

  1. Merge → main has 0.6.8-rc.3 across 4 files
  2. git tag v0.6.8-rc.3 && git push origin v0.6.8-rc.3 → release.yml builds (~22 min) → publishes prerelease
  3. Edit auto-gen release notes on github.com
  4. gh workflow run refresh-release-notes.yml -f tag=v0.6.8-rc.3 → polished notes propagate into latest.json for the in-app dialog

Third internal-tester pre-release. Adds on top of rc.2:
- Linux/macOS auto-restart after install (#73) -- closes the "stuck at
  100%" bug where the install completed but the running process kept
  the old binary.
- Teal banner + dialog badge for prerelease updates (#74) -- visual
  consistency with the sidebar PRE-RELEASE indicator.

Closes the V2-237 install path on Linux. Tested on Ubuntu 25.10 with
the rc.1 -> rc.2 upgrade in #73.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Nic-dorman
Nic-dorman merged commit 705dfcc into main May 1, 2026
4 checks passed
@Nic-dorman
Nic-dorman deleted the chore/bump-0.6.8-rc.3 branch May 1, 2026 08:56
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