chore(release): bump to v0.2.0 - #43
Conversation
First release carrying the in-app updater. Bumps every version location so
the built app reports 0.2.0 and matches the v0.2.0 tag that latest.json is
derived from (release.yml uses VERSION=${TAG#v}). A v0.2.0/v0.1.0 mismatch
would make a fresh install try to "update" to itself.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe project version is consistently bumped from 0.1.0 to 0.2.0 in workspace metadata, the UI package, the Tauri crate, and the Tauri application configuration. ChangesVersion Metadata
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
There was a problem hiding this comment.
Pull request overview
Cuts release v0.2.0 by bumping the application/workspace version metadata from 0.1.0 → 0.2.0 across Rust (workspace + Tauri crate), Tauri config, and the UI’s npm package metadata so the built app and release-tag-derived updater manifest stay in sync.
Changes:
- Bumped Rust workspace package version to
0.2.0and updated selected entries in the rootCargo.lock. - Bumped Tauri app version to
0.2.0intauri.conf.jsonand the Tauri crate’sCargo.toml/Cargo.lock. - Bumped UI npm package version to
0.2.0inpackage.json/package-lock.json.
Reviewed changes
Copilot reviewed 4 out of 7 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| Cargo.toml | Updates workspace package version to 0.2.0. |
| Cargo.lock | Updates some workspace crate versions to 0.2.0, but lock regeneration appears incomplete. |
| apps/microbridge-ui/src-tauri/tauri.conf.json | Updates app-reported version to 0.2.0 (used by updater comparison). |
| apps/microbridge-ui/src-tauri/Cargo.toml | Updates Tauri crate version to 0.2.0. |
| apps/microbridge-ui/src-tauri/Cargo.lock | Updates microbridge-ui to 0.2.0, but lock regeneration appears incomplete for local/workspace deps. |
| apps/microbridge-ui/package.json | Updates npm package version to 0.2.0. |
| apps/microbridge-ui/package-lock.json | Updates lockfile version metadata to 0.2.0. |
Files not reviewed (1)
- apps/microbridge-ui/package-lock.json: Generated file
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Bumps every version location
0.1.0 → 0.2.0to cut v0.2.0 — the first release that carries the in-app updater and publisheslatest.json.Why the bump has to match the tag
release.ymlderives the updater manifest version from the tag (VERSION="${TAG#v}"), while the built app reports its version fromtauri.conf.json. If those disagree, a fresh v0.2.0 install would seelatest.json's0.2.0as newer than its own0.1.0and try to update to itself. So this bumps both sides together.Locations bumped (7 files)
apps/microbridge-ui/src-tauri/tauri.conf.json— the one the updater comparesapps/microbridge-ui/package.json+package-lock.jsonapps/microbridge-ui/src-tauri/Cargo.toml+Cargo.lockCargo.toml([workspace.package]) +Cargo.lock(daemon crates)Version-only change; no code touched. CI covers the build.
After merge
Tag
v0.2.0→release.ymlrebuilds and republishes everything from one build: new signed/notarized DMG, the app tarball Homebrew installs, the updater artifacts, andlatest.json. First real exercise of the PR #42 signing/manifest pipeline. Achore(brew): bump formula to v0.2.0PR auto-opens after publish sobrew upgradecatches up to the same release.🤖 Generated with Claude Code
Summary by CodeRabbit