[feat] Semver Syncing

[lorenzolewis]

Describe the problem

Dramatic reenactment of a potential future Discord thread:

Woot plugins! Woot packages! Oh wait, more packages. Errrrmmm what version goes with what? Do I have the right Tauri CLI? Wait, why is the CLI and the API version different? Oh, that's how it's supposed to be. But I'm getting an error from the camera plugin I just added. Ahhh I need to update the Tauri rust dependency to be compatible!

The plugin system is exciting but it does bring more configuration options and more complexity with that.

There are 2 main issues that I see happening:

1. Support is tough because we have to keep in mind what versions are released and what work with each other
2. Automated checks (maybe via a future CLI addition) are tough because we'd have to create and maintain a mapping of versions

Describe the solution you'd like

Begin versioning all packages to the same major and minor versions. Patches are fine to bump independently and still fairly easy to explain and test (if major and minor match you're fine).

• This would include user-facing Crates and NPM packages (such as tauri, tauri-cli, tauri-api` etc.)
• Plugins (in the workspace such as the upcoming camera plugin: https://github.com/tauri-apps/plugins-workspace/pull/260)
  • Not sure about additional plugins such as log localhost, etc.
• I'm not sure if more "internal" tools would need to be included in this (such as tauri-build, tauri-codegen, tauri-macros, etc.)

Alternatives considered

• Keep the versioning as-is: Difficult to support and DX issues as outlined above
• Match major.minor.patch: A bit too rigid. I can't think of a reason to bump all packages just for a patch update.

Additional context

No response

[lorenzolewis]

After the Working Group call today (meeting notes) we decided to postpone this until we have a conversation around Release Schedules (https://discord.gg/ErH5CAnf?event=1088466123474882591)