Skip to content

[AAASM-3763] 🔖 (release): python-sdk v0.0.1rc1#184

Merged
Chisanan232 merged 6 commits into
masterfrom
v0.0.1/AAASM-3763/release_rc1
Jun 26, 2026
Merged

[AAASM-3763] 🔖 (release): python-sdk v0.0.1rc1#184
Chisanan232 merged 6 commits into
masterfrom
v0.0.1/AAASM-3763/release_rc1

Conversation

@Chisanan232

Copy link
Copy Markdown
Contributor

What

Release-intent version bump for python-sdk to 0.0.1rc1 (PEP 440), coordinated with core v0.0.1-rc.1. Mirrors the prior beta.5 release-intent pattern (#177) and node-sdk's beta.5 PR.

  • pyproject.toml: version = "0.0.1b5"version = "0.0.1rc1" (PEP 440 — rc1, not -rc.1).
  • docs/examples/{agno,haystack,llamaindex-tool-policy,microsoft-agent-framework,smolagents}.md: bump the agent-assembly PyPI pin from >=0.0.1b5>=0.0.1rc1.

Scope — PREP ONLY

This PR does not tag or publish anything.

  • The pyproject.toml version is local-dev metadata only.
  • The real PyPI publish version comes from the Release Python SDK workflow input pypi_version=0.0.1rc1 (with binary_source_tag=v0.0.1-rc.1), dispatched manually after this merges and after a go decision.
  • uv.lock is intentionally untouched (no lockfile churn).
  • Source code is intentionally untouched: agent_assembly/__init__.py still carries __version__ = "0.0.1b5" (left out of this prep-only scope; note that prior PR [AAASM-3706] 🔖 (release): python-sdk 0.0.1b5 #177 bumped it in lockstep — flagging for the release operator).
  • Historical changelog entry ## 0.0.1-beta.5 in docs/compatibility/release-notes.md is left in place (legitimate history).

How to verify

python3 -c "import tomllib;print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])"
# -> 0.0.1rc1

Closes AAASM-3763

🤖 Generated with Claude Code

@codecov

codecov Bot commented Jun 26, 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

🔍 Code Review — Claude Code

Release-intent (prep-only) bump → v0.0.1rc1 · ticket AAASM-3763

  • CI: ✅ 22 pass, 0 fails (the initial uv sync failure was fixed by regenerating uv.lock).
  • Scope:pyproject.toml 0.0.1b5 → 0.0.1rc1, agent_assembly/__init__.py __version__ in lockstep, uv.lock root-version entry updated (required — uv.lock pins the project's own version; minimal diff, no dependency churn), + 5 docs/examples/* pins. Matches the prior beta.5 convention ([AAASM-3706] 🔖 (release): python-sdk 0.0.1b5 #177 also updated __version__ + uv.lock).
  • Side-effects: ✅ none — version metadata + docs; the published PyPI version comes from the Release Python SDK workflow pypi_version=0.0.1rc1 dispatch. Only remaining 0.0.1b5 is the historical changelog header.
  • Verdict: ✅ Ready (prep-only).
    Automated review by Claude Code.

@sonarqubecloud

Copy link
Copy Markdown

@Chisanan232

Copy link
Copy Markdown
Contributor Author

🔍 Review addendum — Claude Code

Two additions since the prior review (the release-notes step was initially missed — see #177 for the convention):

  • Release-notes entry added — new ## 0.0.1-rc.1 section in docs/compatibility/release-notes.md (additions-only, past entries untouched), summarizing the beta→rc promotion + core v0.0.1-rc.1 pin + the real delta since beta.5 (AAASM-3685 TLS-required, AAASM-3686 CI SHA-pinning, AAASM-3722 SBOM fix). No invented content.
  • SKILL codifiedrelease-runbook/SKILL.md now has an explicit "Add the new release-notes section" step before the "Leave the history alone" rule, so this step isn't ambiguous/missed in future releases.

CI: ✅ 21 pass, 0 fails. Verdict unchanged: ✅ Ready (prep-only).
Automated review by Claude Code.

@Chisanan232 Chisanan232 merged commit d465e71 into master Jun 26, 2026
28 checks passed
@Chisanan232 Chisanan232 deleted the v0.0.1/AAASM-3763/release_rc1 branch June 26, 2026 01:39
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