Repository navigation
chore(release): bump version to 0.1.1 - #10
Merged
Merged
Conversation
Ships the i18n (11 languages + Arabic RTL, #7) and Windows portable install location picker (#8) work on top of the released v0.1.0. Bumps all version sources in lockstep — package.json, package-lock.json, tauri.conf.json, Cargo.toml, Cargo.lock — so the built app version matches the v0.1.1 tag that drives latest.json (mismatch would loop the updater).
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.
Release prep for v0.1.1 — bumps the version across all sources of truth in lockstep:
What ships in 0.1.1 (on top of released v0.1.0)
Why bump all five
`release.yml` builds the app version from `tauri.conf.json` but `latest.json`'s version comes from the git tag (`vX.Y.Z` → `X.Y.Z`). If they diverge, the updater advertises a version the installed build doesn't match and loops. Keeping every source at 0.1.1 avoids that.
After merge: tag `v0.1.1` on `main` and push it to trigger the signed/notarized release build.