chore(master): release sdk-python 0.1.2 - #580
Conversation
|
Your Claude subscription has hit its usage limit. It resets at 12am (UTC). Re-trigger Pullfrog after the reset, or add an Add repo secret → · Model settings → · Setup docs → · Ask in Discord →
|
Greptile SummaryThe PR prepares the Python SDK 0.1.2 release.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| .release-please-manifest.json | Updates the Python SDK release component from 0.1.1 to 0.1.2 consistently with package metadata. |
| sdk/python/CHANGELOG.md | Adds the generated release notes and comparison link for Python SDK 0.1.2. |
| sdk/python/pyproject.toml | Bumps the distribution version to 0.1.2 with no dependency or build configuration changes. |
| sdk/python/uv.lock | Synchronizes the editable root package version with pyproject.toml at 0.1.2. |
Reviews (4): Last reviewed commit: "chore: update lockfiles for release" | Re-trigger Greptile
644b711 to
0e4d5f1
Compare
|
Your Claude subscription has hit its usage limit. It resets at 12am (UTC). Re-trigger Pullfrog after the reset, or add an Add repo secret → · Model settings → · Setup docs → · Ask in Discord →
|
bbe3ed6 to
cedb66b
Compare
|
Your Claude subscription has hit its usage limit. It resets at 12am (UTC). Re-trigger Pullfrog after the reset, or add an Add repo secret → · Model settings → · Setup docs → · Ask in Discord →
|
7d20c55 to
0a5999a
Compare
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — this is the first pullfrog review on PR #580, so the whole release-please delta was reviewed rather than a slice of it. Two bot commits, four files, all generated.
- Bumped the Python SDK to
0.1.2across all four version sites —.release-please-manifest.json,sdk/python/pyproject.toml, the rootarcboxentry insdk/python/uv.lock, and the newCHANGELOG.mdsection. All four agree. - Refreshed
uv.lockin a follow-up commit —39f98a7d(chore: update lockfiles for release) touches only the root version line, which is exactly what the plainuv lockin.github/workflows/release-please.ymlis documented to produce. This is load-bearing:release-sdk-python.ymlbuilds withuv sync --locked, so a stale lock would reject the tagged tree and the release would never publish. - Landed the accumulated changelog for
sdk-python-v0.1.1...v0.1.2— 7 features, 7 fixes, 4 test commits, plus docs and CI entries.
Three things I checked that could have gone wrong here and didn't:
- No hardcoded version constant drifts out of sync —
sdk/python/src/arcbox/__init__.py:50derives__version__fromimportlib.metadata.version("arcbox"), sopyproject.tomlis the only authoritative site. No stray0.1.1literal survives anywhere undersdk/pythonoutside the changelog. - The patch-level bump despite 7
featcommits is intentional, not a miscategorization:release-please-config.jsonsetsbump-minor-pre-majorandbump-patch-for-minor-pre-major, which folds features into a patch bump on a0.xline. Cargo.lockis correctly absent — the root crate version is unchanged, so the lockfile job had nothing to write there.
Claude Opus | 𝕏

🤖 I have created a release beep boop
0.1.2 (2026-08-10)
Features
Bug Fixes
Tests
Documentation
Continuous Integration
This PR was generated with Release Please. See documentation.