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. Managed0.7.1,0.7.0and0.6.0entries migrate while custom/local/object entries and unrelated settings remain intact. Use this core'sengram setup pito preserve a custom same-name npm source across installation (#2374). - 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.
At publication, gentle-engram@0.8.0 is available under npm's candidate tag; a read-only public registry check shows latest still at 0.7.0. Promotion of 0.8.0 to latest is pending human browser-based 2FA and was not performed by this release. The matching core installer pins 0.8.0 explicitly.
Provenance
- Previous core:
v3.7.1->a5d4fa7be7f7e41054f5578ce3d21b7da616bb1d - Release target:
v3.7.2->c6ba9e3c0e98ffa0d5591481d8670a575e7b70b0 - Release workflow:
Releaserun 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 tointernal/setup. - Included work: #2374
Full comparison: v3.7.1...v3.7.2