|
| 1 | +# CogniRelay v1.4.9 Release Notes |
| 2 | + |
| 3 | +Release date: 2026-04-27 |
| 4 | + |
| 5 | +CogniRelay v1.4.9 adds the packaging and publication surfaces needed for a |
| 6 | +first PyPI and MCP Registry release, while preserving the existing source |
| 7 | +checkout deployment path. |
| 8 | + |
| 9 | +## Added |
| 10 | + |
| 11 | +- Added PyPI project metadata with a sanitized `README-PYPI.md` long |
| 12 | + description and `cognirelay` console entrypoint. |
| 13 | +- Added a thin `cognirelay` package wrapper with `cognirelay serve` and |
| 14 | + `python -m cognirelay serve`, delegating to the existing `app.main:app` |
| 15 | + runtime. |
| 16 | +- Added root `server.json` metadata for MCP Registry publication, including |
| 17 | + local Streamable HTTP transport, positional `serve` startup metadata, and |
| 18 | + required `COGNIRELAY_REPO_ROOT` environment metadata. |
| 19 | +- Added `tools/validate_server_json.py` for local validation against the |
| 20 | + committed MCP Registry schema URL. |
| 21 | + |
| 22 | +## Changed |
| 23 | + |
| 24 | +- Extended `tools/prepare_release.py` to validate package versions, |
| 25 | + dependencies, `server.json`, the PyPI ownership marker, and publishable tree |
| 26 | + safety before release. |
| 27 | +- Updated installation documentation for source, PyPI, and production |
| 28 | + hardening paths, including durable `COGNIRELAY_REPO_ROOT` guidance and the |
| 29 | + local Streamable HTTP-only MCP Registry posture. |
| 30 | +- Added wheel and sdist artifact checks so packaged releases include only the |
| 31 | + intended runtime assets and source-only documentation/deploy files. |
| 32 | + |
| 33 | +## Security And Privacy |
| 34 | + |
| 35 | +- Removed tracked `data_repo/` runtime state from the Git source surface while |
| 36 | + preserving local operator files on disk. |
| 37 | +- Added publishable-tree safety checks that block tracked runtime state, |
| 38 | + generated databases, logs, token/key files, build residue, and private |
| 39 | + artifacts before publication. |
| 40 | +- Sanitized PyPI metadata so the published long description does not expose |
| 41 | + local runtime-state paths, audit/log paths, capsule paths, or token file |
| 42 | + locations. |
| 43 | +- Added runtime guardrails so installed-package startup refuses unsafe runtime |
| 44 | + state roots under package or `site-packages` paths before creating state. |
| 45 | + |
| 46 | +## Notes |
| 47 | + |
| 48 | +- No PyPI upload, MCP Registry publication, or GitHub Release publication is |
| 49 | + performed by the code change itself; those remain explicit manual release |
| 50 | + steps. |
| 51 | +- Runtime MCP protocol support remains `2025-06-18` and `2025-11-25`. The |
| 52 | + `2025-12-11` value used by `server.json` is the MCP Registry metadata schema, |
| 53 | + not a CogniRelay runtime protocol version. |
| 54 | + |
| 55 | +## Verification |
| 56 | + |
| 57 | +Release preparation should pass: |
| 58 | + |
| 59 | +```bash |
| 60 | +git diff --check |
| 61 | +./.venv/bin/python -m ruff check app tests tools agent-assets |
| 62 | +./.venv/bin/python -m unittest discover -s tests -v |
| 63 | +./.venv/bin/python tools/validate_server_json.py |
| 64 | +./.venv/bin/python -m build |
| 65 | +./.venv/bin/python -m twine check dist/* |
| 66 | +``` |
0 commit comments