Skip to content

docs: record verified v0.5.0 release surfaces - #85

Draft
ebeirne wants to merge 1 commit into
masterfrom
docs/release-truth-v0.5.0
Draft

docs: record verified v0.5.0 release surfaces#85
ebeirne wants to merge 1 commit into
masterfrom
docs/release-truth-v0.5.0

Conversation

@ebeirne

@ebeirne ebeirne commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

What changed

  • Records the publicly verified v0.5.0 release across PyPI, Go, Maven Central, GitHub Releases, GHCR, and the MCP Registry.
  • Updates install instructions, release docs, changelog, citation metadata, Glama/MCP pins, and release-status tests.
  • Keeps npm at its observed public version, 0.4.0, until trusted publishing is configured and v0.5.0 is independently verified.

Why

The source tree is v0.5.0, but release truth must come from public registry state rather than successful workflow logs. This draft prevents Lians from advertising artifacts that consumers cannot actually install.

User impact

Consumers receive accurate, ecosystem-specific installation commands now. Once npm v0.5.0 is live, this branch will be amended so every SDK surface is synchronized.

Validation

  • python scripts/check_release_contract.py
  • python -m pytest agentmem/tests/test_published_release_status.py -q (8 passed)
  • python -m ruff check agentmem/tests/test_published_release_status.py scripts/check_published_artifacts.py
  • python scripts/check_published_artifacts.py
  • JSON/YAML parsing and git diff --check

python scripts/check_published_artifacts.py --require-source-sync currently has one intentional blocker: npm is publicly 0.4.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants