ci(verify): stage CLI bundle resources before cargo steps (issue 17) - #40
Merged
Conversation
added 2 commits
September 5, 2026 02:07
The verify job cargo compiles of the Tauri crate validate tauri.conf.json bundle.resources, but the five declared files were never staged in CI (locally frontend/scripts/prebuild.mjs does it during npm run build), so every main push failed at "Run Tauri crate tests". Insert a fail-closed staging step after "Build CLI" copying the five resources into frontend/src-tauri/bin/. Docs synced: build-and-release.md CI section + AGENTS.md Tauri-shell bullet.
…y (issue 17)
Run 33904993947 proved the five CLI resources stage correctly (5/5 logged)
and the resource gate passed, but compile then hit a second gate:
tauri::generate_context! (main.rs:1409) panics when frontendDist
("../../dist", repo-root dist/) does not exist - the real dist/ is only
produced by "Build frontend", which runs after the cargo steps. Seed a
dist/index.html placeholder in the same staging step; vite build
overwrites it with real output later.
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.
Root cause
verify job's
cargo test/cargo checkonfrontend/src-tauritriggerstauri_build::build()(build.rs), which validates the five files declared intauri.conf.json → bundle.resourcesunderfrontend/src-tauri/bin/. Locallyfrontend/scripts/prebuild.mjsstages them duringnpm run build/tauri build, but the verify job runs cargo directly — every main push failed at "Run Tauri crate tests" withresource path bin/env-manager-cli.exe doesn't exist(run 33880367303).Fix
env-manager-cli.exe/.dll/.runtimeconfig.json/.deps.jsonfrombin/Release/net10.0-windows/andAGENTS.cli.mdfrom the repo root intofrontend/src-tauri/bin/; any missing file exits 1 (5/5 check).build.mjs/prebuild.mjsuntouched); no changes to cargo test/check assertions ortauri.conf.json.docs/build-and-release.mdCI section +AGENTS.mdTauri-shell bullet.Part of architecture-recovery ticket 17 (main push CI always green).