store: release 0.1.1 — first signed release through push-to-deploy #3
Loading…
Reference in a new issue
No description provided.
Delete branch "ctrl-agent/metronome:chore/store-0.1.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bumps
store/VERSION0.1.0 → 0.1.1. No store code change.Purpose: exercise the release-on-merge + push-to-deploy path end to end for the first time. On your merge (instance-signed, operator-only branch protection) the workflow releases
store-v0.1.1, builds twice and proves the binary reproducible, publishes the two assets, then rings the polymeter-sync guest's doorbell with thedeploy-polymeter-synccert minted 2026-10-21 (principal mapped on that host only, forced command, source 10.20.30.61/32). The guest's installer verifies the merge signature against the pinned instance key, checks the sha256, installs into a versioned dir and switchescurrentfrom the unsigned floorstore-v0.1.0.Expected after merge:
readlink /usr/local/libexec/polymeter-sync/current→store-v0.1.1, health check green, https://kv.varasys.io/ still 200. The hub verifies and reports; rollback is the installer's own (symlink back to 0.1.0) if the health check fails.🤖 Generated with Claude Code