[release] 🔖 (release): Bump version to 0.0.1rc4 - #243
Conversation
Advance the checked-in version literals to 0.0.1rc4 (PEP 440) and regenerate uv.lock ahead of the release-python.yml workflow_dispatch that consumes core tag v0.0.1-rc.4. Keeps pyproject.toml, __version__, sonar.projectVersion, and the lockfile's own pinned version in lockstep so the SonarCloud gate, uv sync, and the next Case-B release base do not lag the published wheel.
Add the 0.0.1-rc.4 release-notes section (headline: cp313/cp314 release wheel matrix + drift guard, AAASM-4446/4453), bump the agent-assembly install pins in the five framework examples that carry a literal pin, and advance the governed base-image tag examples to v0.0.1-rc.4 so the docs track the release.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Release-prep review — v0.0.1-rc.4 version bumpReviewed against the 1. CI — PASS. All checks settled green, including the critical drift-guard 2. Scope (version correctness) — COMPLETE & CORRECT. All 8 footprint files advanced
Remaining 3. Side effects — CLEAN. 4. FE — N/A. Version literals + doc markdown only; no rendered UI change. No Playwright run. Dispatch confirmation: Verdict: APPROVE (prep PR). Do not merge/dispatch from this review.— Claude Code |
1 participant
Description
Version-bump prep-only PR for the PyPI
0.0.1rc4release (core tag itconsumes:
v0.0.1-rc.4). Advances every checked-in version literal from0.0.1rc3so
masterdoes not lag the wheel thatrelease-python.ymlwill stamp.Bumped (per the
sdk-only-releaseskill's required footprint):pyproject.tomlversion->0.0.1rc4agent_assembly/__init__.py__version__->0.0.1rc4uv.lockregenerated (project's own pinned version ->0.0.1rc4)sonar-project.propertiessonar.projectVersion->0.0.1rc4docs/compatibility/release-notes.md- new## 0.0.1-rc.4section (headline:cp313/cp314 release wheel matrix + drift guard, AAASM-4446 / AAASM-4453)
docs/examples/{agno,haystack,llamaindex-tool-policy,microsoft-agent-framework,smolagents}.md>=0.0.1rc3->>=0.0.1rc4docs/guides/container-base-image.md- governed base-image tag examplesv0.0.1-rc.3->v0.0.1-rc.4Static rc.3 references are intentionally left as-is: the
.github/scripts/*.shPEP-440 conversion test fixtures (assert the
v0.0.1-rc.3<->0.0.1rc3mapping),
docs/development/docs-macros.md's explicit "what NOT to template"historical illustration, and the
source-facts-guard.jspublished-range comment(rc.4 is not published yet).
This PR precedes the
release-python.ymlworkflow_dispatch(
pypi_version=0.0.1rc4,binary_source_tag=v0.0.1-rc.4,dry-runfirst). It doesnot publish, tag, or dispatch anything. The
bot/aa-ffi-pin-v0.0.1-rc.4FFI-pinbump (PR #241) is already on
master, so the Case-A coordination order is satisfied.Type of Change
Breaking Changes
Related Issues
agent-assemblycore tagv0.0.1-rc.4.Testing
Validated locally:
uv lockleaves a consistent lockfile (only the project's ownversion line changed);
import agent_assemblysucceeds and__version__ == "0.0.1rc4";grep -rn '0.0.1rc3'across the repo returns only the intentionally-static fixtures /historical references noted above; all pre-commit hooks (isort, autoflake, black,
mypy, uv-lock) pass on the version-bump commit.
Checklist