fix(ci): restore releaseBody so latest.json notes is populated#34
Merged
fix(ci): restore releaseBody so latest.json notes is populated#34
Conversation
When the release workflow was split into create-release / release-desktop jobs (50df230), the `releaseBody` input on tauri-action was dropped along with the now-unused `tagName` / `releaseDraft` / `releaseName` inputs. `releaseBody` is what tauri-action passes into the bundler to fill the `notes` field of `latest.json`. Without it, every release since v1.2.0 has shipped a `latest.json` with `"notes": ""`, so the desktop in-app update dialog has been showing the "Bug fixes and improvements." fallback instead of the actual changelog. Wire `needs.create-release.outputs.changelog` (which is already produced by the create-release job) back into tauri-action so future releases populate the in-app changelog automatically. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
The release workflow refactor in 50df230 ("ci: parallelize Linux/Windows builds") split the single
releasejob intocreate-release+release-desktop. In the process, thereleaseBodyinput ontauri-apps/tauri-action@v0was removed alongside the (now-unused)tagName/releaseName/releaseDraftinputs.releaseBodyis what tauri-action passes through to the Tauri bundler to fill thenotesfield oflatest.json. Without it, every release from v1.2.0 onward has shipped alatest.jsonwith"notes": "", so the desktop in-app update dialog has been silently falling back to the placeholder "Bug fixes and improvements." string instead of showing the actual changelog.(v1.3.0 was patched manually post-build β see release notes.)
The fix
Wire
needs.create-release.outputs.changelog(whichcreate-releasealready produces) intotauri-action:with: releaseId: ${{ needs.create-release.outputs.release_id }} + releaseBody: ${{ needs.create-release.outputs.changelog }} tauriScript: cargo tauriTest plan
latest.json'snotesfield is non-emptyπ€ Generated with Claude Code