Skip to content

[AAASM-3706] 🔖 (release): python-sdk 0.0.1b5#177

Merged
Chisanan232 merged 3 commits into
masterfrom
v0.0.1/release/b5
Jun 24, 2026
Merged

[AAASM-3706] 🔖 (release): python-sdk 0.0.1b5#177
Chisanan232 merged 3 commits into
masterfrom
v0.0.1/release/b5

Conversation

@Chisanan232

Copy link
Copy Markdown
Contributor

Description

Release-intent PR for python-sdk 0.0.1b5 (git tag v0.0.1-beta.5).

This PR bumps the checked-in version and adds release notes only. It does not tag, publish, or trigger any release workflow. After merge and owner go-ahead, the operator dispatches release-python.yml manually (command below).

Changes:

  • pyproject.toml + agent_assembly/__init__.py __version__: 0.0.1b40.0.1b5
  • uv.lock regenerated to the new version
  • docs/compatibility/release-notes.md: new 0.0.1-beta.5 section

Headline: five new framework adapters since b4 — LlamaIndex (AAASM-3536), Agno (AAASM-3537), Microsoft Agent Framework (AAASM-3538), Smolagents (AAASM-3539), Haystack (AAASM-3540) — plus token-hygiene (AAASM-3642), supply-chain attestation/SBOM/pip-audit (AAASM-3568), SDK-version passthrough (AAASM-3683), and the release-autopublish fix (AAASM-3503).

Type of Change

  • 🚀 Release

Breaking Changes

  • No

Related Issues

  • Related JIRA ticket: AAASM-3706

Testing

  • Manual testing performed
    • uv lock resolved cleanly (agent-assembly 0.0.1b4 -> 0.0.1b5)
    • uv sync succeeded
    • python -c "import agent_assembly; print(agent_assembly.__version__)"0.0.1b5
    • ruff check clean on changed files
    • pre-commit hooks passed on commit (isort/black/mypy/uv-lock)
  • No tests required (explain why): version-bump + docs only; no behavioral change.

Checklist

  • Code follows project style guidelines
  • Self-review completed
  • Documentation updated if needed
  • All tests passing

Release mechanics note: tag/publish happens AFTER this PR merges + owner go. The publish is operator-dispatched (release-python.yml is workflow_dispatch-only; the AAASM-3503 fix removed the core repository_dispatch auto-publish trigger). Do NOT merge or tag this PR as part of CI.

🤖 Generated with Claude Code

Chisanan232 and others added 2 commits June 24, 2026 23:10
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@codecov

codecov Bot commented Jun 24, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@Chisanan232

Copy link
Copy Markdown
Contributor Author

✅ Claude Code review — release-prep: python-sdk 0.0.1b5 (AAASM-3706)

CI: all green (0 failures, 22 checks) — Analyze (python), unit + integration test matrix (3.13), Build documentation, build-native-core, Dependency advisory audit (pip-audit), PEP 561 compliance, CodeQL, codecov.

Scope (release-intent — no tag/publish): pyproject.toml + agent_assembly/__init__.py 0.0.1b40.0.1b5, uv.lock regenerated, docs/compatibility/release-notes.md b5 section (headlining the 5 new framework adapters: llamaindex/agno/haystack/microsoft_agent_framework/smolagents). uv sync resolves, __version__ reads 0.0.1b5, ruff + pre-commit clean.

Release mechanics confirmed: release-python.yml is workflow_dispatch-only; published version comes from the pypi_version input (checked-in bump is for repo/badge honesty). AAASM-3503 PASS — no repository_dispatch auto-publish (fix PR #157 merged); core's tag can't trigger a python publish.

Publish (after merge + core beta.4 release + FFI-pin merge + owner go): gh workflow run release-python.yml -R ai-agent-assembly/python-sdk -f pypi_version=0.0.1b5 -f binary_source_tag=v0.0.1-beta.4 (dry-run=true first). binary_source_tag set explicitly to the new core — the "latest" default is unreliable.

Verdict: ✅ Ready to merge. ⛔ Publish only at GATE 2 (after core beta.4 ships).

@sonarqubecloud

Copy link
Copy Markdown

@Chisanan232

Copy link
Copy Markdown
Contributor Author

🔄 Update — new-adapter example pins (Claude Code)

Extended this PR (head f622b0b) with a project-wide pin sweep. Fixed 4 example docs that pinned versions which don't contain their adapter (the adapter is new in b5, absent from published b4 — verified against the v0.0.1-beta.4 tag):

  • docs/examples/agno.md >=0.0.1b4>=0.0.1b5
  • docs/examples/haystack.md >=0.0.1b2>=0.0.1b5
  • docs/examples/microsoft-agent-framework.md >=0.0.1b2>=0.0.1b5
  • docs/examples/smolagents.md >=0.0.1b2>=0.0.1b5

llamaindex was already >=0.0.1b5 (AAASM-3695). b4-shipped adapters (crewai/google_adk/langchain/langgraph/mcp/openai_agents/pydantic_ai) left at their valid pins. CI re-ran green (21 pass, 0 fail). Still ✅ ready to merge.

@Chisanan232 Chisanan232 merged commit ca1fc15 into master Jun 24, 2026
28 checks passed
@Chisanan232 Chisanan232 deleted the v0.0.1/release/b5 branch June 24, 2026 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant