Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix incorrect versions of plugins in migration v1.0 to beta guide #2079

Open
Viijay-Kr opened this issue Apr 20, 2024 · 0 comments
Open

Fix incorrect versions of plugins in migration v1.0 to beta guide #2079

Viijay-Kr opened this issue Apr 20, 2024 · 0 comments
Labels
bug Does it fix inaccurate content or fix a bug? good first issue Is it good for beginners to take up?
Milestone

Comments

@Viijay-Kr
Copy link

Viijay-Kr commented Apr 20, 2024

The version information of some plugins in migration guide is misleading . The auto migration command also fails to install the right plugins .
Manually adding the dependencies to the cargo.toml using the specified version number from the doc also fails .
Thanks to rust-analyzer I was able to add the correct version number.

I think this doc should convey the correct version numbers other than just specifying "2" as version number.

https://beta.tauri.app/guides/upgrade-migrate/from-tauri-1

Currently the following plugins resulted in a failure for me if I follow the migration documentation and use "2" as version

tauri = { version = "2.0.0-beta", features = [] }
tauri-plugin-clipboard-manager = { version = "2.1.0-beta.1" }
tauri-plugin-shell = "2.0.0-beta.3"
[target."cfg(not(any(target_os = \"android\", target_os = \"ios\")))".dependencies]
tauri-plugin-global-shortcut = { version = "2.0.0-beta.3" }
tauri-plugin-http = { version = "2.0.0-beta.5" }
@Viijay-Kr Viijay-Kr changed the title Fix incorrect version in migration v1.0 to beta documentation Fix incorrect versions of plugins in migration v1.0 to beta guide Apr 20, 2024
@simonhyll simonhyll added this to the Version 2.0 milestone May 3, 2024
@simonhyll simonhyll added bug Does it fix inaccurate content or fix a bug? good first issue Is it good for beginners to take up? labels May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Does it fix inaccurate content or fix a bug? good first issue Is it good for beginners to take up?
Projects
Status: 💪 Ready
Development

No branches or pull requests

2 participants