V0.10.3
AmritaCore v0.10.3 Release Summary
We are pleased to announce the release of AmritaCore 0.10.3! This update brings enhanced AI‑generated content governance, improved MCP client reliability, extended thinking configuration for OpenAI‑compatible models, and a smoother documentation experience. Below are the key highlights.
🆕 New Features
-
AIGC Content Licensing Policy
Introduced a formal policy (POLICY_OF_AIGC, AACLP v1.0) that clarifies the use of AI‑generated content in contributions. The policy sets clear guidelines for core business logic, documentation, tests, and review obligations, ensuring transparency and quality control. -
Enhanced Thinking/Reasoning Configuration for OpenAI Adapters
The OpenAI adapter now supports additional reasoning parameters:thinking_type("enabled"/"disabled") andenable_thinkingare passed viaextra_bodyfor models that support these fields.reasoning_effortremains available for compatibility.
This provides finer control over reasoning behaviour across different model families.
-
Local Search in Documentation
Added a built‑in local search provider to the VitePress documentation site (both English and Chinese versions), making it easier to find relevant guides and API references.
⚡ Improvements
-
MCP Client Connection Resilience
- Introduced an async lock (
_connect_lock) to make_connect()idempotent and safe for concurrent calls. - Added a dedicated
_refresh_tools()method to update the tool cache without forcing a full reconnect. - Improved cleanup logic to avoid potential deadlocks during connection teardown.
These changes make MCP‑based tool integration more robust in multi‑task environments.
- Introduced an async lock (
-
Simplified AIGC Policy References
TheCONTRIBUTING.mdfile now links to the separate policy document instead of repeating the full text, keeping the contributing guide concise while centralising governance rules. -
Code Cleanup
Removed staleTODOcomments inagent.pyandconfig.pyto reduce clutter.
🐛 Bug Fixes
-
MCP Client
Fixed a race condition that could occur when multiple coroutines attempted to connect simultaneously. The new locking mechanism ensures a single connection is established and reused correctly. -
Test Adjustments
Updated the MCP test suite to reflect the new idempotent connection behaviour, removing an obsolete exception expectation.
📄 Documentation
- Added a dedicated AIGC Content Licensing Policy page (
POLICY_OF_AIGC) and cross‑linked it fromREADME.mdandCONTRIBUTING.md. - Added an
X‑Powered‑Byheader comment inconsts.pyto credit the underlying frameworks (AmritaCore & AmritaSense). - Enabled local search on the documentation site for both English and Chinese locales.
🔧 Other Changes
- Version bump:
0.10.2→0.10.3 - Issue Template – Minor formatting fix in the
future-request.ymltemplate. - Lock file – Updated
uv.lockto reflect the new version.
🙏 Acknowledgements
We thank all contributors and community members who provided feedback on the AIGC policy and MCP client improvements. Your input helps make AmritaCore more reliable and transparent.
For the full changelog, please see the commit history. As always, we welcome your contributions – please review our updated guidelines and happy building!
Pull Requests
- docs: update AIGC content licensing policy references by @JohnRichard4096 in #100
- Update POLICY_OF_AIGC by @JohnRichard4096 in #101
- Make MCP connections concurrency-safe and extend thinking config by @JohnRichard4096 in #107
Full Changelog: 0.10.2...0.10.3