Skip to content

v3.7.2

Latest

Choose a tag to compare

@github-actions github-actions released this 14 Nov 00:26
· 9 commits to main since this release
c6ba9e3

Engram 3.7.2

Packaging-only patch release with the matching gentle-engram@0.8.0 companion.

  • Pi setup: the installer pin moves to npm:gentle-engram@0.8.0. Managed 0.7.1, 0.7.0 and 0.6.0 entries migrate while custom/local/object entries and unrelated settings remain intact. Use this core's engram setup pi to preserve a custom same-name npm source across installation (#2374).
  • Pi companion 0.8.0: shared-mode startup prefers engram run -d so engram ps, stop, logs and restart manage the server the companion starts, and ENGRAM_DEFER_MEMORY=1 defers Memory Protocol injection while the mem_* tools stay registered (#2368, #2371).
  • No runtime change: the only core runtime source changes are the installer pin and its managed predecessor entry. The server, store, protocol, other CLI commands and build inputs are unchanged, and the runtime contract asset is unchanged.

Back up data and configuration before upgrading. Restart an existing server through its supervisor and verify the running server version. Pi users can run engram setup pi, then restart Pi.

Download the archive matching your OS/architecture and verify it against checksums.txt. See the release and rollback policy.

gentle-engram@0.8.0 was first published under npm's candidate tag and, after the published pair was inspected, promoted to latest; a public registry readback now shows both latest and candidate at 0.8.0. The matching core installer pins 0.8.0 explicitly.

Verification

  • Previous core: v3.7.1 -> a5d4fa7be7f7e41054f5578ce3d21b7da616bb1d
  • Release target: v3.7.2 -> c6ba9e3c0e98ffa0d5591481d8670a575e7b70b0
  • Release workflow: Release run 43533869927 succeeded; module metadata tidy verification, the published-companion gate and GoReleaser all completed successfully.
  • Verification: all six published core archives and their checksums were downloaded and 6/6 checksums matched; the published npm tarball's SHA-512 matches the registry metadata; the Homebrew core 3.7.2 formula was verified.
  • Source range: three commits and 15 changed files from v3.7.1 (+246/-44); core-runtime changes are limited to internal/setup.
  • Included work: #2374, with #2368 and #2371 shipped in the Pi companion
  • Limits: these checks do not claim an installed upgrade test on real user installations in every environment.

Full comparison: v3.7.1...v3.7.2