You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we informally decided in a voting in the working group discord channel to release a new major version of Tauri as a consequence of breaking changes we need to write an announcement that describes:
Motivation
Changelog
Migration path
Backwards (in)compatibility issues/drop
Context from working group discussions:
We need to upgrade/replace gtk3/gtk-rs which has breaking changes and we currently have 3ish options to go forward with:
Get upstream maintainers of gtk-rs to update to a recent glib version or transfer to tauri (unlikely but not impossible) - would be a short term solution also keeping v1 supported
Migrate to gtk4-rs and other upgrade behind feature flags in multiple crates to release in a minor and keep v2 supported
Migrate to gtk4-rs and other upgrades with a v3 major release
We can combine 1 and 2/3 to keep v1/v2 supported with security relevant updates of glib but depends on upstream actors.
Also note that gtk3 is unmaintained since last year and the upgrade is kinda unavoidable over time, this just accelerates the process.
Context Motivation
The initial movement was caused by unsound behavior in glib < 0.2 leading to an acceleration of updating our dependencies and removing part of our older no longer required dependencies.
As we informally decided in a voting in the working group discord channel to release a new major version of Tauri as a consequence of breaking changes we need to write an announcement that describes:
Context from working group discussions:
We need to upgrade/replace
gtk3
/gtk-rs
which has breaking changes and we currently have 3ish options to go forward with:gtk-rs
to update to a recentglib
version or transfer to tauri (unlikely but not impossible) - would be a short term solution also keeping v1 supportedgtk4-rs
and other upgrade behind feature flags in multiple crates to release in a minor and keep v2 supportedgtk4-rs
and other upgrades with a v3 major releaseWe can combine 1 and 2/3 to keep v1/v2 supported with security relevant updates of
glib
but depends on upstream actors.Also note that gtk3 is unmaintained since last year and the upgrade is kinda unavoidable over time, this just accelerates the process.
Context Motivation
The initial movement was caused by unsound behavior in glib < 0.2 leading to an acceleration of updating our dependencies and removing part of our older no longer required dependencies.
We are touching all/most of these crates either by updating gtk or by removing it as a dependency.
The text was updated successfully, but these errors were encountered: