• v1.10.5 fdb1f94479

    Morphit v1.10.5
    All checks were successful
    morphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 50s
    morphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 40s
    morphit-ci / Integration tests (real Postgres 16) (push) Successful in 41s
    morphit-ci / ansible-lint (playbook quality gate) (push) Successful in 17s
    morphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 34m7s
    morphit-release / Build + publish release tarball (push) Successful in 37m34s
    Stable

    agorise released this 2026-08-08 05:51:01 +00:00 | 35 commits to main since this release

    Signed by agorise
    GPG key ID: 53524E1F1017EB9C

    Morphit v1.10.5

    Theme: guided (ansible) installs now advertise the correct relay account, so a new instance is accepted by its peers on the first probe instead of being rejected.

    This is a maintenance release. There are no database migrations and no breaking changes.

    Fixed

    Ansible-installed instances now report their own relay account. Every instance publishes a relay account in /v1/instance, and peers refuse to trust an instance whose published relay account doesn't match the account that signed its on-chain registration (an anti-impersonation check). The guided ansible installer set the operator tag and account name but never wrote the indexer's relay-account setting, so it silently fell back to the canonical default — meaning a fresh ansible instance advertised the wrong account and every other node rejected its health probe with a "relay account mismatch." The installer now writes the correct value (the same account the relay signs with), matching what the manual morphit-ops wizard already did. A guard was added so no install writer can omit it again.

    Notes

    • No database migrations. No breaking changes.
    • Only the guided (ansible) install path was affected; manual morphit-ops installs already set this correctly.
    • An existing ansible instance can fix this without upgrading by setting MORPHIT_INDEXER_RELAY_ACCOUNT to its own account and restarting the indexer.
    Downloads