Guildhall 0.13.0

Guildhall 0.13.0 makes the selected release a stricter shared contract and makes publishing the app artifact a repeatable command instead of a manual sequence.

What changed

• Saved release decisions: the selected scope is stored as project state and reused by the API, guildhall status, and the main project surfaces.
• Owner-held reviews: a spec waiting for approval stays an explicit owner decision. Unattended runs cannot approve it or route around it.
• Historical shipped releases: shipped membership and proof remain closed while later work is selected, reshaped, or inspected.
• Bounded reads: compact project surfaces consume revisioned projections and withhold stale totals instead of rebuilding the whole project during a page load.
• Automated release artifacts: the publish command builds and verifies the npm package, macOS package, GitHub release assets, and matching runtime image digest before npm publication.

Upgrade

npm install -g guildhall@0.13.0

Or use the macOS installer:

curl -fsSL https://raw.githubusercontent.com/matthew-dean/guildhall/main/scripts/install.sh | GUILDHALL_VERSION=0.13.0 sh

Then open Guildhall and follow any project migration shown in the app.

Learn the release flow

Ship a release walks through selection, scope, readiness, repository follow-up, shipping, and the optional next release.

The stricter shipped-state UI and interrupted-publish recovery are part of the 0.13.1 patch, not the original 0.13.0 package.