This release includes 2 breaking changes for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+4 more
Affected surfaces
Summary
AI summaryAll MEMMCP_ environment variable prefixes have been renamed to CONTEXTLATTICE_.
Full changelog
ContextLattice v3.2.7
This release updates public v3 naming and deployment clarity for registries like Glama.
Included
- PR #93: canonical prefix cutover in public repo.
- Replaced all
MEMMCP_/memmcp_prefixes withCONTEXTLATTICE_/contextlattice_across tracked files. - Updated scripts, docs, packaging, and service env wiring to canonical ContextLattice naming.
- Preserved endpoint pinning and service flow (
http://127.0.0.1:8075).
- Replaced all
- Production auth model clarified:
MEMMCP_ENVnow supportsdevelopment | production | strictsemantics in public docs/runtime references.- API-key requirement can be opt-in for production posture.
Validation on release commit
cd services/gateway-go && go test ./...: passpython3 -m pytest -q services/orchestrator/tests/test_orchestrator_retrieval.py -k validate_security_posture: pass
Notes for Glama reviewers
- Canonical env namespace is now ContextLattice-first.
- Release metadata and docs align with testable-default deployment posture.
Breaking Changes
- Renamed all `MEMMCP_` / `memmcp_` prefixes to `CONTEXTLATTICE_` / `contextlattice_` in tracked files, scripts, docs, packaging, and service env wiring.
- `MEMMCP_ENV` removed; use `CONTEXTLATTICE_ENV` with values `development | production | strict`.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About sheawinkler/ContextLattice
Private-by-default memory and context layer for agents with Go/Rust runtime, staged retrieval across fused data backends, and long-horizon context continuity.
Related context
Related tools
Beta — feedback welcome: [email protected]