agorise/morphit
agorise/morphit
Watch
1
0
Fork
You've already forked morphit
 0
Code Issues Pull requests Projects Releases 186 Packages Wiki Activity Actions
186 releases 186 tags
  • v1.17.12 7d828b9f20

    Morphit v1.17.12
    All checks were successful
    morphit-ci / Supply-chain audit gate (fail on new high/critical) (push) Successful in 32s
    Details
    morphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 55s
    Details
    morphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 48s
    Details
    morphit-ci / Integration tests (real Postgres 16) (push) Successful in 1m46s
    Details
    morphit-ci / ansible-lint (playbook quality gate) (push) Successful in 58s
    Details
    morphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 34m59s
    Details
    morphit-release / Build + publish release tarball (push) Successful in 35m31s
    Details
    Stable

    agorise released this 2026-09-17 00:41:20 +00:00 | 3 commits to main since this release

    Signed by agorise
    GPG key ID: 53524E1F1017EB9C

    Morphit v1.17.12

    Fixes a mistake introduced in v1.17.11 that stopped an upgrade finishing its
    final checks. No protocol or consensus change.

    Fixed

    • The last step of an upgrade completes again. v1.17.11 added a check that
      skips an irrelevant test on privacy-only instances. On an ordinary instance
      that check looked at a value that had not been set yet, which stopped the
      script on the spot. The release itself was never at risk — it was published,
      recorded on-chain and pinned before this point — but the instance stopped
      before confirming it serves the new version over Tor and I2P, so other
      instances could not be sure they could fetch it from you. Upgrading applies
      the fix; nothing else is needed.
    • The retry advice now works. The message shown when that step fails pointed
      at a command that could not run on its own. It now names the menu entry that
      does the job, and says plainly what was left unfinished rather than implying
      the whole thing failed.
    • No more "new version of npm available" after an upgrade. That notice was
      already meant to be silenced, but it was silenced too late in the process to
      take effect. It advised an upgrade you should not perform, since each release
      ships with the versions it was tested against.

    Notes

    • No protocol/consensus change. Everything here is operator-facing.
    • If your last upgrade ended with a warning about the self-seed step, this
      release is the fix. After upgrading, that step runs to completion on its own.
    Downloads