Repository navigation
fix(release): verify macOS icons with the pinned package CLI - #4025
Merged
wgqqqqq merged 1 commit intoNov 20, 2026
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.
Summary
The v1.0.12 Intel Mac release job failed because the icon suite expected both workspace packages to pin Tauri CLI 2.11.4. Desktop now pins 2.12.6 for the Linux Wayland bundler fix. Installer still pins 2.11.4. Both real Mac icon probes passed on the runner. Failing job
Check each manifest against the CLI resolved from that package after the frozen install. When rebuilding a release tag, use the verification script from the workflow revision and load the application, dependencies and icon inputs from the tagged checkout. This allows the v1.0.12 Mac packages to be recovered at their original source commit.
Verification
Changes apply to release verification. Remote runtime behavior is outside the affected path.