Skip to content

Migrate native app from Tauri v1 to v2#1649

Open
grMLEqomlkkU5Eeinz4brIrOVCUCkJuN wants to merge 1 commit into
bridge-core:mainfrom
grMLEqomlkkU5Eeinz4brIrOVCUCkJuN:tauri-v2-migration
Open

Migrate native app from Tauri v1 to v2#1649
grMLEqomlkkU5Eeinz4brIrOVCUCkJuN wants to merge 1 commit into
bridge-core:mainfrom
grMLEqomlkkU5Eeinz4brIrOVCUCkJuN:tauri-v2-migration

Conversation

@grMLEqomlkkU5Eeinz4brIrOVCUCkJuN
Copy link
Copy Markdown

@grMLEqomlkkU5Eeinz4brIrOVCUCkJuN grMLEqomlkkU5Eeinz4brIrOVCUCkJuN commented Jun 1, 2026

Description

  • Bump tauri and tauri-build to 2; split the v1 api-all surface into the plugins actually used (fs, dialog, updater, process)
  • Convert tauri.conf.json to the v2 schema and add capabilities
  • Port the frontend to the v2 plugin imports and the new fs, updater, and window APIs
  • Drop window-shadows in favour of the built-in window shadow
  • Pin tauri-runtime 2.10.1 and wry 0.54.0 to match the published tauri-runtime-wry 2.10.1; newer versions of either break the build
  • Update CI to libwebkit2gtk-4.1-dev and the v2 signing environment variables

Motivation

Builds the desktop app against webkit2gtk-4.1 (in the official repos) instead of the removed webkit2gtk-4.0, so it no longer needs the old library compiled from source. (It is incredibly annoying to wait for legacy version with no precompile binary on my i3 6th gen machine, but I understand that everyone are busy. <3)

Additional Context

  • Initially made for myself, but thought devs might be interested, thanks for making an editor dedicated to minecraft modding, I really loved this project.
  • I also chose to target the main branch directly since the dev branch for some reason has a weird commit history, let me know if I should redo this part. Apologies in advance.

Thank you for your time <3

Builds the desktop app against webkit2gtk-4.1 (in the official repos)
instead of the removed webkit2gtk-4.0, so it no longer needs the old
library compiled from source.

- Bump tauri and tauri-build to 2; split the v1 api-all surface into
  the plugins actually used (fs, dialog, updater, process)
- Convert tauri.conf.json to the v2 schema and add capabilities
- Port the frontend to the v2 plugin imports and the new fs, updater,
  and window APIs
- Drop window-shadows in favour of the built-in window shadow
- Pin tauri-runtime 2.10.1 and wry 0.54.0 to match the published
  tauri-runtime-wry 2.10.1; newer versions of either break the build
- Update CI to libwebkit2gtk-4.1-dev and the v2 signing env vars
@bolt-new-by-stackblitz
Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@grMLEqomlkkU5Eeinz4brIrOVCUCkJuN grMLEqomlkkU5Eeinz4brIrOVCUCkJuN changed the title Migrate native app from Tauri v1 to v2 feat: Migrate native app from Tauri v1 to v2 Jun 1, 2026
@grMLEqomlkkU5Eeinz4brIrOVCUCkJuN grMLEqomlkkU5Eeinz4brIrOVCUCkJuN changed the title feat: Migrate native app from Tauri v1 to v2 Migrate native app from Tauri v1 to v2 Jun 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant