agorise/morphit
agorise/morphit
Watch
1
0
Fork
You've already forked morphit
 0
Code Issues Pull requests Projects Releases 145 Packages Wiki Activity Actions
145 releases 145 tags
  • v1.10.9 c1f3ecf6a8

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

    agorise released this 2026-08-09 20:21:01 +00:00 | 31 commits to main since this release

    Signed by agorise
    GPG key ID: 53524E1F1017EB9C

    Morphit v1.10.9

    Theme: a clean, trustworthy upgrade. The upgrade output no longer prints alarming-looking (but harmless) warnings that could make a new operator think something went wrong.

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

    Fixed

    No more "getcwd: cannot access parent directories" errors during an upgrade. The upgrade backs up the install directory by renaming it, but the running tool was still "inside" that directory — so every helper it started afterward complained that its working directory had vanished. The upgrade now steps out to a stable directory before the rename, so those errors are gone. (They were always harmless — the upgrade completed correctly — but they read like a broken install.)

    Quieter dependency install. The upgrade's dependency step printed several "npm warn deprecated" lines about third-party packages Morphit doesn't control and an operator can't act on. Those are now suppressed during an upgrade; genuine errors still show. (Developer builds keep the full output.)

    No stray "large chunk" build hint during an upgrade. The frontend build's chunk-size hint — useful when developing, noise when upgrading — is no longer shown during an operator upgrade.

    The "is the new frontend actually being served?" check no longer gives a false "could not verify." That check ran the instant the web container restarted, usually before it had finished coming back up, and reported it couldn't confirm. It now waits and retries briefly, so a successful upgrade reports a clean confirmation instead.

    Notes

    • No database migrations. No breaking changes.
    • These are all cosmetic-output fixes; v1.10.8 upgrades completed correctly despite the noise.
    Downloads