Repository navigation
chore: prepare v0.4.6 Linux compatibility release - #75
Merged
Merged
Conversation
This was referenced Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepare a new patch version for the Linux compatibility fix merged in #74. Synchronize Python, npm, Cargo, Tauri, lockfile and frontend versions to 0.4.6 and add release notes describing the Ubuntu 22.04/glibc 2.35 baseline and offline startup validation scope.
Published v0.4.5 assets remain unchanged. This PR does not publish a release or request AppImageHub retesting. Fresh release builds must pass the existing source/version, installer SHA-256, native startup and notarization gates before publication.
Validation: version-only preparation; Linux package and audit CI must pass for this commit. Final release assets and their hashes remain to be verified.