fix(build): allow metadata-only application builds - #1
Open
zackarychapple wants to merge 2 commits into
Open
Conversation
Package Changes Through e373029There are 9 changes which include tauri with patch, tauri-utils with patch, tauri-build with patch, tauri-plugin with patch, tauri-macros with patch, tauri-codegen with patch, @tauri-apps/cli with patch, tauri-cli with patch, tauri-bundler with minor Planned Package VersionsThe following package releases are the planned based on the context of changes in this pull request.
Add another change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
zackarychapple
marked this pull request as ready for review
August 10, 2026 02:24
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
Attributes::build_application_artifacts(bool), defaulting totrueWhy
A library-only package may need
tauri_build::try_buildfor ACL/context metadata without owning an application executable. Running the existing application-artifact path from that package can emit invalid binary-only Cargo directives and create unordered duplicate writers for staged app payloads.The real application package remains on the default-enabled path, so this changes no normal Tauri build pipeline.
Validation
cargo +stable fmt --package tauri-build -- --checkcargo +1.88.0 test -p tauri-build --all-features --locked— 10 unit tests plus doctestcargo +1.88.0 clippy -p tauri-build --all-targets --all-features --locked --no-deps -- -A clippy::uninlined-format-args -D warningscargo +nightly-2026-05-05 check -p tauri-build --target x86_64-pc-windows-msvc --all-features --locked