Closed atilafassina closed 2 months ago
I don't think this is necessary, package.json
can go without a version
and the Tauri CLI can lookup the version from Cargo.toml
if tauri.conf.json
doesn't have one. In MacroGraph I just bump Cargo.toml
and a workflow reads the version number from there, creates a tag, a release, etc.
I don't think this is necessary,
package.json
can go without aversion
and the Tauri CLI can lookup the version fromCargo.toml
iftauri.conf.json
doesn't have one. In MacroGraph I just bumpCargo.toml
and a workflow reads the version number from there, creates a tag, a release, etc.
ohhh, absolutely! I will borrow that!
To keep all 3
version
declarations in sync, it's best to have a version bumping script and thus also pushing Notes / Changelog to CrabNebula.Cargo.toml
version.- [ ] Updatespackage.json
version.- [ ] Updatestauri.conf.json
version.