fix(release): sync tauri.conf.json into the version-bump set#92
Merged
Conversation
The cut-release skill bumped package.json and src-tauri/Cargo.toml for v0.5.1 but missed src-tauri/tauri.conf.json (still at 0.5.0). tauri-action templates the bundle filenames from tauri.conf.json's version field, so the v0.5.1 release was built with artifacts named Claude.Code.Trace_0.5.0_*.dmg etc. Sync tauri.conf.json to 0.5.1 to match the rest of the workspace, and add the file to the cut-release skill's version-bearing files table and Phase 3 bump step so future releases stay aligned.
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
2 participants
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.
Why
src-tauri/tauri.conf.jsonwas missing from thecut-releaseskill'sversion-bearing files table, so v0.5.1 shipped with all artifacts named
Claude.Code.Trace_0.5.0_*even thoughpackage.jsonandsrc-tauri/Cargo.tomlhad been bumped to0.5.1.tauri-actionreadstauri.conf.json'sversionfield when stamping bundle filenames atbuild time, so it has to bump in lockstep with the other version files.
What
src-tauri/tauri.conf.jsonfrom0.5.0to0.5.1to bring mainin sync with the rest of the workspace.
.claude/skills/cut-release/references/project-shape.md(now four version-bearing files instead of three) and to
.claude/skills/cut-release/steps/phase3-bump-versions.mdso futurecut-releaseruns include it automatically.Test plan
npx oxfmtcleannpx oxlintcleannpx tsc --noEmitcleannpx vitest run— 366 passedcargo clippy --manifest-path src-tauri/Cargo.toml— 0 warningscargo test --manifest-path src-tauri/Cargo.toml— 397 passedA separate force-push of tag
v0.5.1(ontorelease/v0.5.1-rebuild)re-runs the release pipeline so the v0.5.1 release page gets correctly
named artifacts.
Generated by Claude Code