-
Morphit v1.17.13
StableAll checks were successfulmorphit-ci / Supply-chain audit gate (fail on new high/critical) (push) Successful in 34smorphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 55smorphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 48smorphit-ci / Integration tests (real Postgres 16) (push) Successful in 1m51smorphit-ci / ansible-lint (playbook quality gate) (push) Successful in 54smorphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 35m0smorphit-release / Build + publish release tarball (push) Successful in 37m53sagorise released this
2026-09-17 06:31:21 +00:00 | 2 commits to main since this releaseGPG key ID: 53524E1F1017EB9CMorphit v1.17.13
Stops an upgrade interrupting operators who sign their warrant canary on a
separate computer. No protocol or consensus change.Fixed
- An upgrade no longer stops to ask about your warrant canary if you already
have one. If you sign your canary on another machine and upload it, a
redeploy clears the copy on the server until you upload the next one. The
upgrade only remembered as far back as the previous install, so if you ever
skipped an upload, the next upgrade concluded you had never had a canary and
offered to create one on the server — which would have made a second signing
key competing with your real one, and stopped an unattended upgrade waiting
for an answer. Your instance now remembers permanently that you have a canary,
and also checks whether your live site is serving one. A brand-new instance
with no canary at all is still offered one, as before.
Notes
- No protocol/consensus change. Everything here is operator-facing.
- If a recent upgrade asked you about setting up a canary and you sign yours
elsewhere, answering "no" was correct. After this release it will not ask again.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- An upgrade no longer stops to ask about your warrant canary if you already