test

[hijzy]

Description

Please include a summary of the change, the problem it solves, the implementation approach, and relevant context. List any dependencies required for this change.

Related Issue (Required): Fixes #issue_number

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (does not change functionality, e.g. code style improvements, linting)
• Documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Unit Test
• Test Script Or Test Steps (please provide)
• Pipeline Automated API Test (please provide)

Checklist

• I have performed a self-review of my own code | 我已自行检查了自己的代码
• I have commented my code in hard-to-understand areas | 我已在难以理解的地方对代码进行了注释
• I have added tests that prove my fix is effective or that my feature works | 我已添加测试以证明我的修复有效或功能正常
• I have created related documentation issue/PR in MemOS-Docs (if applicable) | 我已在 MemOS-Docs 中创建了相关的文档 issue/PR（如果适用）
• I have linked the issue to this PR (if applicable) | 我已将 issue 链接到此 PR（如果适用）
• I have mentioned the person who will review this PR | 我已提及将审查此 PR 的人

Reviewer Checklist

• closes #xxxx (Replace xxxx with the GitHub issue number)
• Made sure Checks passed
• Tests have been provided

[Memtensor-AI]

🤖 Open Code Review

Target: PR #2240
Task: e177fe1bd4301089
Base: dev-v2.0.29
Head: chore/bump-v2.0.29

🔍 OpenCodeReview found 1 issue(s) in this PR.

---

1. pyproject.toml (L7)

The version "2.0.29.test" is not a valid PEP 440 version string. The .test suffix is not a recognized pre-release or post-release segment in PEP 440 (which allows suffixes like .dev, .a, .b, .rc, .post).

This will likely cause issues when:

1. Packaging and publishing to PyPI — tools like twine and build will either reject it or warn about it.
2. Downstream dependency resolution — package managers (e.g., pip) may fail to parse or compare this version correctly.

Suggestion: Use a PEP 440-compliant pre-release or dev version identifier instead, for example:

• 2.0.29.dev0 — for a development/test build
• 2.0.29a1 — for an alpha release
• 2.0.29rc1 — for a release candidate

If this version bump is only for local/internal testing and is not intended for publishing, it should not be merged into the main branch as-is.

💡 Suggested Change

Before:

version = "2.0.29.test"

After:

version = "2.0.29.dev0"

Generated by cloud-assistant via Open Code Review.

[Memtensor-AI]

⚠️ Automated Test Results: NO TEST SCOPE

Automated tests were not run because the changed files do not map to an executable test scope.

Details: No executable test scope maps to the changed files. Automated tests were not run; add env.yaml source_mapping + execution for this path family, then rerun. Changed files: (none detected)
Manual review or env.yaml source_mapping/execution coverage is required before merge.

Branch: chore/bump-v2.0.29