feat(linux): harden AppImage release quality - #185
Merged
Conversation
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.
What changed
.DirIconand.desktopsymlinks in generated AppImagesappdir-lintvalidation script with checksum verificationWhy
The AppImage catalog submission mounted the v1.6.0 artifact but rejected it because
.DirIconwas a broken absolute symlink. This is the defect fixed upstream in Tauri #15596. The catalog PR was closed rather than leaving a known-failing submission open.Local validation
npm test— 162 passednpm run build:frontendnpm run lint— 0 errors, 41 existing warningsbash -n scripts/validate-linux-appimage.shgit diff --checkThe new
Build, lint, and launch AppImagecheck provides the real Linux artifact validation for this PR.