chore(release): 5.0.0 - #262
Merged
Merged
Conversation
All three manifests, because release.yml compares them and exits 1 when they disagree: package.json, src-tauri/tauri.conf.json and src-tauri/Cargo.toml, plus both lockfiles. Verified with the workflow's own check. A major bump rather than a minor one. Since 4.0.0 the pipeline moved to WebAssembly, so the app ships Radiance, hdrgen and dcraw_emu inside itself and there are no tool paths to configure; the product was renamed to LumiLab; RAW conversion moved into a worker behind a cache that survives reloads; storage moved from files under the Tauri config directory into IndexedDB; and the routes were renamed. The version the Settings page and the About box report both derive from these, so nothing else needs changing: next.config.js inlines package.json's value for the browser build. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Every tag before this one is a bare vN.N.N: v4.0.0, v3.1.0, v3.0.0, v2.0.0.
The workflow used Tauri's own app-v${version} convention, so the next release
would have been the first to break that, and a release history that changes
naming partway stops sorting and stops being guessable from a link.
The release title follows the tag for the same reason.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
adulbrich
added a commit
that referenced
this pull request
Aug 7, 2026
…mp (#264) #262 edited the version with a JSON serializer, which re-serialised the whole file and expanded "scope": ["**"] across three lines. Biome's formatter wants it inline, so lint has failed on main since that merge, and every branch cut from main inherits it. That went unnoticed because #262's own CI was reported as passing when only the Vercel checks had run; the Actions run failed and was not re-read before merge. A version bump has no business reformatting the file it edits. If this is done again by hand, change the one line rather than round-tripping the document. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
adulbrich
added a commit
that referenced
this pull request
Aug 7, 2026
* chore(release): 5.0.0
All three manifests, because release.yml compares them and exits 1 when they
disagree: package.json, src-tauri/tauri.conf.json and src-tauri/Cargo.toml,
plus both lockfiles. Verified with the workflow's own check.
A major bump rather than a minor one. Since 4.0.0 the pipeline moved to
WebAssembly, so the app ships Radiance, hdrgen and dcraw_emu inside itself and
there are no tool paths to configure; the product was renamed to LumiLab; RAW
conversion moved into a worker behind a cache that survives reloads; storage
moved from files under the Tauri config directory into IndexedDB; and the
routes were renamed.
The version the Settings page and the About box report both derive from these,
so nothing else needs changing: next.config.js inlines package.json's value for
the browser build.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* ci(release): tag releases v5.0.0, not app-v5.0.0
Every tag before this one is a bare vN.N.N: v4.0.0, v3.1.0, v3.0.0, v2.0.0.
The workflow used Tauri's own app-v${version} convention, so the next release
would have been the first to break that, and a release history that changes
naming partway stops sorting and stops being guessable from a link.
The release title follows the tag for the same reason.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
adulbrich
added a commit
that referenced
this pull request
Aug 7, 2026
…mp (#264) #262 edited the version with a JSON serializer, which re-serialised the whole file and expanded "scope": ["**"] across three lines. Biome's formatter wants it inline, so lint has failed on main since that merge, and every branch cut from main inherits it. That went unnoticed because #262's own CI was reported as passing when only the Vercel checks had run; the Actions run failed and was not re-read before merge. A version bump has no business reformatting the file it edits. If this is done again by hand, change the one line rather than round-tripping the document. Co-authored-by: Claude Opus 5 (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
1 participant
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.
Bumps all three manifests plus both lockfiles.
release.ymlreads the version frompackage.jsonand then failscreate-releaseoutright ifpackage.json,src-tauri/tauri.conf.jsonandsrc-tauri/Cargo.tomldisagree, so this is the change that has to land before a release can start at all. Verified locally with the workflow's own check:Nothing else needs touching:
next.config.js:13inlinespackage.json's value into the browser build, and the desktop reads it from Tauri, so the Settings page and the About box both follow.Why major
Since
4.0.0the pipeline moved to WebAssembly, so the app now ships Radiance,hdrgenanddcraw_emuinside itself and there are no tool paths to configure; the product was renamed to LumiLab; RAW conversion moved into a worker behind a cache that survives reloads; storage moved from JSON files under the Tauri config directory into IndexedDB; and the routes were renamed.Two things this deliberately does not do
It does not delete the stale draft release. There is an untagged "App v4.0.0" draft from the 2026-08-01 workflow run, built from post-tag
mainand labelled 4.0.0. It should probably go before a 5.0.0 release is published, but deleting a release is not something to slip into a version bump.It does not change the tag scheme.
release.ymlcreatesapp-v${version}, so this would publish asapp-v5.0.0, while every historical tag is a barev4.0.0,v3.1.0and so on. Worth deciding deliberately rather than discovering after the fact; changing it is a one-line edit to the workflow.Ordering
Worth landing after #260 and #261, so the release carries the header-provenance fix and the corrected PRD.
🤖 Generated with Claude Code