store: release 0.1.1 — first signed release through push-to-deploy #3

Merged
casey merged 1 commit from ctrl-agent/metronome:chore/store-0.1.1 into main 2026-10-21 22:45:31 +00:00
Collaborator

Bumps store/VERSION 0.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 the deploy-polymeter-sync cert 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 switches current from the unsigned floor store-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

Bumps `store/VERSION` 0.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 the `deploy-polymeter-sync` cert 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 switches `current` from the unsigned floor `store-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](https://claude.com/claude-code)
No store code change. The bump exists to exercise the release-on-merge + push-to-deploy
path end to end for the first time: the instance-signed merge releases store-v0.1.1, CI rings
the polymeter-sync guest's doorbell with the deploy-polymeter-sync cert (minted 2026-10-21),
and the guest's installer verifies the signature, checksums, installs and switches from the
unsigned floor store-v0.1.0.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
casey merged commit d0a14b394d into main 2026-10-21 22:45:31 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
varasys/metronome!3
No description provided.