Files
aitbc/docs/releases/README.md
aitbc 96088f4501
Some checks failed
API Endpoint Tests / test-api-endpoints (push) Successful in 46s
CLI Tests / test-cli (push) Failing after 2s
Documentation Validation / validate-docs (push) Failing after 9s
Documentation Validation / validate-policies-strict (push) Failing after 12s
Package Tests / Python package - aitbc-agent-sdk (push) Successful in 24s
Package Tests / Python package - aitbc-core (push) Successful in 19s
Package Tests / Python package - aitbc-crypto (push) Successful in 10s
Package Tests / Python package - aitbc-sdk (push) Successful in 16s
Package Tests / JavaScript package - aitbc-sdk-js (push) Successful in 5s
Package Tests / JavaScript package - aitbc-token (push) Successful in 10s
Production Tests / Production Integration Tests (push) Successful in 17s
Python Tests / test-python (push) Successful in 8s
Security Scanning / security-scan (push) Successful in 46s
Multi-Node Blockchain Health Monitoring / health-check (push) Failing after 3s
Integration Tests / test-service-integration (push) Failing after 11m28s
docs-validation: expand curated markdown scope to include all documentation hubs
Add all documentation subdirectories to the curated markdown linting targets, replacing the previous exclusion-based approach with comprehensive coverage. Update validation to check for required README files across all hubs and verify priority documentation metadata markers. Implement lazy loading for optional dependencies (numpy, redis, bcrypt, jwt, websockets) in agent-coordinator and related modules to improve startup
2026-04-27 11:57:36 +02:00

1.4 KiB

Release Notes

Level: All Levels
Prerequisites: None
Estimated Time: 5-15 minutes
Last Updated: 2026-04-27
Version: 1.0

🧭 Navigation Path:

🏠 Documentation Home📋 ReleasesYou are here

breadcrumb: Home → Releases → Overview


🎯 See Also:


📦 Release History

Read the release notes newest-first:


🧱 Purpose

This directory records versioned release notes, migration context, and milestone summaries.


🚀 Next Steps

  • Start with the newest release note when checking change history.
  • Use release notes to understand migration and operational implications.
  • Keep future release notes linked from the master index.

Last updated: 2026-04-27
Version: 1.0
Status: Release index