Repository navigation
Release v0.16.2 - #548
Release v0.16.2#548
Conversation
Bumps [mem0ai](https://github.com/mem0ai/mem0) from 2.0.5 to 2.0.18. - [Release notes](https://github.com/mem0ai/mem0/releases) - [Commits](mem0ai/mem0@v2.0.5...v2.0.18) --- updated-dependencies: - dependency-name: mem0ai dependency-version: 2.0.18 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Synchronize released main history through the normal green develop CI controls. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Preserve automatic data-only PR evaluation with trusted configuration, protected templates, credential-safe destinations, and revision-bound status provenance. Relates to #499. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Distinguish administrator-controlled nonsecret values from independently checked secret resources. Do not imply a service connection check protects a group after the connection is removed. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Grant AGENTOPS_CI_CONFIG only to the named trusted preparation step and restrict eval consumers to their exit-code output. Cover generic and prompt-agent PR cloud gates in the regression matrix. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…/mem0ai-2.0.18 Integrate the reviewed E2E sample dependency update into develop after the complete CI matrix passed. No changes to the separate security fix or stable release. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Integrate the reviewed PR evaluation isolation fix after refreshing current develop and passing full local and CI validation. Keep the migration requirements explicit and the change under Unreleased. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
The maintainer explicitly confirmed installing, evaluating and approving the exact staged 0.16.2 VSIX in the release session. This applies to candidate c2b10c9 and VSIX SHA256 79fbd2c4d58799cb1ff713033f78c048cb675dacdad200cd52db217c024efc77. Final-head staging 42306196445 succeeded. Required local full suite on that head: 1710 passed, one expected missing-MCP negative-test skip because MCP is installed. Actual TestPyPI hashes, packaged security payload, isolated wheel installation and CLI smoke tests were verified. Live main/develop refs and unused stable version were rechecked immediately before the normal merge. This records the actual human candidate evaluation, not a fabricated formal self-approval or Marketplace deployment approval. The protected marketplace-release approval remains required. Issue #499 stays open until actual publication is verified, then closes with the mandatory consumer workflow migration and external-control caveats. |
Release v0.16.2
Patch release from validated
developcommit644a075d1f1095be8f440ecac9d959a0b0a0736d. Final candidate:c2b10c9aef3ba37539b804bb1d623541f90f22c8.Scope
mem0airequirement from 2.0.5 to 2.0.18.116abf0c9977927f5307a8966a1677794eb492bdand0ed254fa1cb27bc1f9c355fb770933cd280b2155.Validation and actual staged artifacts
0.16.2.dev10match the official published SHA256 digests.0.16.2, pre-release, with exactly seven unique skill registrations and all referenced files present. SHA256:79fbd2c4d58799cb1ff713033f78c048cb675dacdad200cd52db217c024efc77.v0.16.2pushed on the verified main merge commit. Tagging publishes Python irreversibly without an approval pause.origin/develop..origin/mainlog and correct Unreleased structure.marketplace-releasedeployment approval, stable Marketplace publication, PyPI publication and GitHub Release verified.Required consumer migration
Installing the new package does not migrate existing copied workflows. Consumers must regenerate the YAML and configure and validate the protected resources and exclusive status identities documented in CI/CD setup. Publishing this code does not configure or demonstrate those controls in consumer organizations. This is not a general prompt-injection defense.
Issue #499 will be closed only after actual release publication is verified, with these migration limitations explicitly recorded. Python Trusted Publishing, Marketplace Entra OIDC, protected deployment approval, shared Azure settings and secrets remain unchanged.