Skip to content

Fix AgencyZero release build and bump 0.8.51 - #209

Closed
pathscale wants to merge 1 commit into
masterfrom
fix/blitz-release-resolution
Closed

pathscale wants to merge 1 commit into
masterfrom
fix/blitz-release-resolution

Conversation

@pathscale

@pathscale pathscale commented Sep 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • align AgencyZero direct Blitz DOM and script dependencies with the 0.4 family required by tauri-runtime-blitz 0.3.2
  • align the standalone Blitz preview to the same family
  • keep all dependency declarations as caret ranges
  • bump AgencyZero to 0.8.51 so the release is unambiguous and guaranteed to trigger

Root cause

A fresh lockless release resolved direct ps-blitz-script ^0.3 to 0.3.6 while tauri-runtime-blitz brought 0.4.2. Rust then saw two incompatible ScriptDocument types.

Validation

  • clean graph contains one ps-blitz-dom and one ps-blitz-script, both 0.4.2
  • cargo pkgid -p az-gui reports 0.8.51 after a fresh lockfile generation
  • cargo check -p az-gui --features blitz-inspector
  • cargo test -p az-gui --features blitz-inspector --no-run
  • cargo fmt --all -- --check
  • cargo fmt --manifest-path apps/blitz-preview/Cargo.toml -- --check
  • cargo clippy --manifest-path apps/blitz-preview/Cargo.toml --all-targets -- -D warnings

The fresh-worktree GUI checks reused the existing generated frontend dist and sidecar binaries; they did not install or launch anything.

@pathscale
pathscale force-pushed the fix/blitz-release-resolution branch from e7593ae to 6b2a3ba Compare September 5, 2026 18:48
@pathscale pathscale changed the title Fix AgencyZero 0.8.50 release build Fix AgencyZero release build and bump 0.8.51 Sep 5, 2026
@pathscale

Copy link
Copy Markdown
Owner Author

Additional local release validation on the PR head (6b2a3ba):

  • built the Stable-profile release bundle with cargo tauri build --features blitz-inspector, CARGO_PROFILE_RELEASE_STRIP=false, and line-table debug info
  • bundle reports 0.8.51; codesign --verify --deep --strict passes; ad-hoc signature is intact; main executable retains 14,248 external symbols
  • build resolved WorkTable 1.0.0-beta.19, WorkTablesIndex 0.0.12, arctic-wt 0.1.9, congee-wt 0.4.4, and the unified Blitz 0.4.2 family
  • updater archive was produced; local updater signing then stopped as expected because TAURI_SIGNING_PRIVATE_KEY exists only in Actions
  • all 18 wt-migrate tests pass
  • both strict-load rejection/rebuild tests pass
  • restored the committed 29 MB QA profile and rebuilt all 17 WorkTable directories successfully: 27,334 rows total, including 5,635 usage-ledger rows, 5,335 cache rows, 5,180 sessions, 4,810 task-log rows, and 2,212 messages

Local test app (not installed or launched): /Users/revenge/code/agencyzero/target/release/bundle/macos/AgencyZero.app.

@pathscale

Copy link
Copy Markdown
Owner Author

Experimental bundle validation is also complete. cargo tauri build --features experimental,blitz-inspector --config tauri.experimental.conf.json produced AgencyZero Experimental.app; it reports bundle id com.pathscale.agencyzero.experimental, version 0.8.51, passes deep/strict code-sign verification, is ad-hoc signed as intended, and retains 14,275 external symbols. As with Stable, only local updater signing stopped for the expected missing private key. The test bundle is at /Users/revenge/code/agencyzero/target/release/bundle/macos/AgencyZero Experimental.app; it was not installed or launched.

@pathscale

Copy link
Copy Markdown
Owner Author

Correction to the aggregate in my preceding validation comment: the listed per-table counts sum to 27,314 rows, not 27,334. The per-table output and all pass/fail results are unchanged.

@pathscale

Copy link
Copy Markdown
Owner Author

Closing in favor of #211. The release-resolution work is superseded there. The remaining preview-only diff mixes ps-blitz 0.4 types with tauri-runtime-blitz 0.3 and is not safe to fold.

@pathscale pathscale closed this Sep 13, 2026
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