Central version bump.
Is your feature request related to a problem? Please describe. Any time a version bump is required. I need to update three locations
-
tauri.conf.json: Build version on the binaries. -
package.json: Version number for github releases -
cargo.toml: I dont think this is honored anywhere, except when using cargo run.
Describe the solution you'd like A central source of truth? Can tauri.conf.json not be a part of package.json?
Additional context My folder setup is unique since, my project was originally a rust project using webview. So at build time I need to restructure my folder like this, so that I can create installers via the build cli.
package.json isn't necessary for tauri, so you don't need to specify a version there (*except currently the tauri action uses package.json to get the version).
The version in tauri.conf.json is optional. By default, it uses the version from Cargo.toml.
The version in Cargo.toml is required by Cargo no matter what, so imo it makes sense to go for that.
While yes. package.json reflects the version shown in the github release.
tauri.conf.json is most likely the version provides by the package meta inside a tauri app provided by the api.
If you specify a version in tauri.conf.json, yes, but otherwise it defaults to Cargo.toml