Skip to content

chore(release): v2.0.1-aio.2#78

Merged
JSONbored merged 1 commit into
mainfrom
codex/release-mem0-v2.0.1-aio.2
May 10, 2026
Merged

chore(release): v2.0.1-aio.2#78
JSONbored merged 1 commit into
mainfrom
codex/release-mem0-v2.0.1-aio.2

Conversation

@JSONbored
Copy link
Copy Markdown
Owner

Summary

  • prepare the formal mem0-aio v2.0.1-aio.2 release
  • update the changelog and CA-facing XML Changes entry

What changed

  • records the security/runtime hardening shipped after v2.0.1-aio.1
  • includes the signed Ubuntu apt-source preservation fix validated by the successful central publish run

Why

The container and template behavior changed, so this needs a formal release tag and GitHub Release rather than only a main-branch image publish.

Validation

  • git diff --check
  • uv run --with pytest --with defusedxml pytest
  • aio-fleet validate-repo --repo mem0-aio
  • aio-fleet trunk run --repo mem0-aio --no-fix

Notes

  • After merge, run aio-fleet control-check with publish enabled for the release commit, then aio-fleet release publish.

@JSONbored JSONbored merged commit b93e72c into main May 10, 2026
3 checks passed
@JSONbored JSONbored deleted the codex/release-mem0-v2.0.1-aio.2 branch May 10, 2026 09:16
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.

1 participant