Skip to content

build: track master instead of pinning revs, and fix the build - #159

Merged
pathscale merged 2 commits into
masterfrom
fix/blitz-bench-rev
Aug 16, 2026
Merged

build: track master instead of pinning revs, and fix the build#159
pathscale merged 2 commits into
masterfrom
fix/blitz-bench-rev

Conversation

@pathscale

Copy link
Copy Markdown
Owner

The az build failed on scripts/check-one-rev-per-git-source.sh:

Cargo.lock resolves a git dependency at more than one revision:
https://github.com/pathscale/tauri-runtime-blitz.git
    71d7bd897fc936b54fc4731e56600b9497e402ad
    9edbec23ce4ca9bcb052a364577fd9a736fd81a3

The engine repin moved apps/gui but not crates/blitz-bench, which still asked for trb at 9edbec2 for blitz-control-protocol. A local cargo check -p az-gui passed because it never touches the bench crate, which is the gap that script exists to cover. apps/blitz-preview was on a third rev (070ab3a).

Rather than repin three manifests by hand again, they now track branch = "master". agent-experimental too. Keeping revs in step manually is what broke the last two builds.

worktable stays pinned and now carries a comment saying why: master has moved to an arctic-wt cargo cannot select alongside this workspace, so branch = "master" fails to resolve rather than building something newer. It is the only rev left in the repo.

Verified locally: one-rev guard passes, cargo clippy --workspace --all-targets --features experimental,webview-runtime -- -D warnings clean, 282 tests pass.

0.8.7.

🤖 Generated with Claude Code

meh added 2 commits August 16, 2026 17:56
The engine repin moved apps/gui but not crates/blitz-bench, which still asked
for tauri-runtime-blitz at 9edbec2 for blitz-control-protocol. Cargo.lock then
carried both revs and check-one-rev-per-git-source.sh failed the build.

Local cargo check -p az-gui passed because it never touched the bench crate,
which is the gap the script exists to cover.

0.8.7.
Four of the five git revs in this workspace were pinned for no reason beyond
inertia, and keeping them in step by hand is what broke the last two builds:
apps/gui, crates/blitz-bench and apps/blitz-preview each named a different
tauri-runtime-blitz rev, and cargo resolving one source at three revisions is
exactly what check-one-rev-per-git-source.sh rejects.

tauri-runtime-blitz (three manifests) and agent-experimental now track master,
so there is nothing to keep in step.

worktable stays pinned and says why in a comment: master has moved to an
arctic-wt cargo cannot select alongside this workspace, so branch = master
fails to resolve rather than building something newer.

clippy -D warnings, 282 tests, and the one-rev guard all pass.
@pathscale
pathscale merged commit 3fa7e46 into master Aug 16, 2026
2 checks passed
@pathscale
pathscale deleted the fix/blitz-bench-rev branch August 16, 2026 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant