Repository navigation
Conversation
Engram 3.7.1 reports unmanaged listeners before lifecycle actions (engram#2351), admits the complete pre-org and v3.4.0 migration catalogs (engram#2338, engram#2350, engram#2354) and builds with the Go 1.26.11 security patch (engram#2353). The six archive digests and sizes match the release checksums.txt, the GitHub asset digests and a local re-hash. The v3.7.1 store keeps schemaVersion 1, and its runtime contract digest is unchanged from 3.7.0, so gentle-engram 0.5.1 and later stay compatible.
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Raises the bundled Engram core pin from 3.7.0 to 3.7.1, the latest Engram release.
Refs #3015
Why
3.7.1 ships 19 commits on top of 3.7.0. The ones that matter for Shell users:
engram serveleft running by an older Shell, whichengram stopcannot manage.rowsresult while the bundled judgment-day skill requestsfindings/evidence#2354: migration admits the complete v3.4.0 and pre-org catalogs and SQLite-quotedsync_chunksheaders. This matters for users upgrading stores created by the 3.5.2 core that v4.7.0 bundles.The runtime contract digest is unchanged from 3.7.0 (
0af9af17…810f), sogentle-engram0.5.1 and later stay compatible.Changes
scripts/installer-downloads.mjsversion3.7.1 and the six archive sha256/size tupleslib/gentle-shell-bundled.tsBUNDLED_ENGRAM_SCHEMAand the runtime-contract table gain3.7.1; 3.7.0 entries keptruntime/gentle-shell-bundled.mjstests/engram-safety.test.tstests/bundled-install.test.ts,tests/installer-posix-bootstrap.test.tsdocs/bundled-install.mdVerification
Archives: all six sha256 digests and sizes match three sources byte for byte: the release
checksums.txt, the GitHub API assetdigest/size, and a localsha256sumof fresh downloads. Separately, the valuesartifactFor("engram", …)returns match the API for all six targets.d1979720dd2f0f240c2ce1544051866155d709b58b30575f617ea4ea5b8f49ca7dfa0ddcf8ede0ad7be53913ee7bf83a4f6e89a419db8c02559fa3e3df848579bc1acef625f16923b2ba548e0c911996b30d65c7c7cf15e949ecbc58136b127bd5023e786af7cefe07a5d46f8064851d5f89be73bdb10af4a148358ed0605583715b6ba35013c853e3607afefdf211923a5d3bef5894b77a55fe2a306b2b05e9ab78c9dabeb0438d9a4712926b40b5354e014b13867f3f3a08d7983087a96114Schema:
v3.7.1:internal/store/store.go:1270declaresconst schemaVersion = 1.Real binary (linux amd64, isolated
HOME, data dir and port):engram versionprintedengram 3.7.1.engram run -dreturned exit 0.GET /runtime-contractreturnedengram.pi-http-runtime/v1, revision 1, digest0af9af176928e98562ab1396d3196efe582dd5d1c5d2c5f8f546ab4ed609810f./healthreported version3.7.1.engram stopreturned exit 0, and the port then refused connections.engram helplistsmigrate-copy.node --experimental-strip-types --test tests/engram-safety.test.ts tests/bundled-install.test.ts tests/gentle-shell-bundled.test.ts tests/installer-posix-bootstrap.test.ts: 281 passed, 0 failed, 1 skipped (a Windows-only test, skipped on Linux).pnpm check:runtime-modules: runtime matches sources.pnpm typecheck: 0 diagnostics.git diff --check: clean.This PR does not cut a release.
Summary by CodeRabbit