archived-tauri/check-plugin-versions.md at 1a3d1a024ebb2a3dd5d15849523a55246d78fda6

mirror of https://github.com/tauri-apps/tauri.git synced 2026-01-31 00:35:19 +01:00

Files

Lucas Fernandes Nogueira bc4afe7dd4 feat(cli): check plugin versions for incompatibilities (#13993 )

* feat(cli): check plugin versions for incompatibilities

check core plugin versions for incompatibilities between Cargo and NPM releases

a plugin NPM/cargo version is considered "incompatible" if their major or minor versions are not equal

on dev we show an warning
on build we error out (with a `--ignore-incompatible-plugins` flag to prevent that)

this is an idea from @oscartbeaumont
we've seen several plugin changes that require updates for both the cargo and the NPM releases of a plugin, and if they are not in sync, the functionality does not work
e.g. https://github.com/tauri-apps/plugins-workspace/pull/2573 where the change actually breaks the app updater if you miss the NPM update

* Use list to get multiple package versions at once

* Fix for older rust versions

* Clippy

* Support yarn classic

* Support yarn berry

* Use `.cmd` only for `npm`, `yarn`, `pnpm`

* Use yarn list without --pattern

* rename

* Extract function `check_incompatible_packages`

* Check `tauri` <-> `@tauri-apps/api`

* incompatible -> mismatched

* run build check in parallel

* rename struct

* Switch back to use sync check and add todo

* Extract to function `cargo_manifest_and_lock`

---------

Co-authored-by: Tony <legendmastertony@gmail.com>

2025-08-17 12:24:40 -03:00

132 B

Raw Blame History

tauri-cli, @tauri-apps/cli

tauri-cli	@tauri-apps/cli
minor:feat	minor:feat

Check installed plugin NPM/crate versions for incompatible releases.

132 B Raw Blame History

132 B

Raw Blame History