[release-cadence] Active release queue

[github-actions]

Release cadence report - 2026-05-12

This issue is generated by .github/workflows/release-cadence.yml.
It schedules readiness review only. Publishing still requires a human.

Current package state

• SDK repo version: 1.2.10
• PyPI latest: 1.2.10
• MCP repo version: 0.2.2
• npm latest: 0.2.2
• Glama API status: 0 indexed tools; env schema present

MCP / Glama train

• Cadence: review every Tuesday.
• Ship when MCP runtime, package metadata, tool schema, registry metadata, or Glama state changed.
• Hold when npm, MCP Registry, and Glama already match the current package.

Checklist:

• Run npm --prefix mcp-server test.
• Run python -m pytest sdk/tests/test_mcp_registry_metadata.py -v.
• Run python scripts/sdk_release_guard.py --check-mcp-npm.
• Verify MCP Registry search reports the current npm version.
• Verify Glama exposes env schema and seven tools.
• Publish a Glama release only after npm and registry state are correct.

SDK train

• Monthly readiness due now: no
• Ship when accumulated runtime, API, docs, examples, or proof changes create user-visible value.
• Hotfix immediately for security, broken install, broken publish, or hosted-ingest contract regressions.

Checklist:

• Run python scripts/generate_pypi_readme.py --check.
• Run python scripts/sdk_release_guard.py.
• Run CI-equivalent tests, lint, and bandit.
• Regenerate sdk/PYPI_README.md when release notes change.
• Confirm PyPI Trusted Publishing and attestations after publish.

Decision

• MCP train ships this week.
• MCP train holds this week.
• SDK train ships this month.
• SDK train holds this month.

Reference: docs/release/cadence.md.