Release 0.3.1 - #153
Merged
Merged
Release 0.3.1#153
Conversation
Everything under [Unreleased] since v0.3.0, rolled into a dated section: the seven findings of the pre-release review in #152 (a handler that raises now refuses in the vendor's dialect instead of crashing to a non-blocking error; Kimi Code's config.toml is read and written as UTF-8 and never truncated by a failed write; TOML block markers match whole lines so one owner cannot claim another's block; parse() and detect() are total over non-object payloads; Gemini command TOML escapes control characters; a diagnostic that cannot be written never pre-empts the refusal; a `*` in repo_root is a directory name). Fixes only, so a patch bump under semver. Version is declared in three places and all three move together: pyproject.toml, src/agentseam/__init__.py, and CITATION.cff, which tests/test_repo_standards.py holds equal to the package. The [Unreleased] compare link becomes the 0.3.1 link. docs/assets/social-preview.{svg,png} are regenerated, not edited: the card renders the version, and the brand-assets check would have failed on the stale one. No behaviour change in this commit. The v0.3.1 tag already on main points at a commit versioned 0.3.0, so it has to be moved to this one after the merge for release.yml to publish 0.3.1. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Jothi Mani Rajendran <250249270+jothimani-rajendran@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The release-prep PR for 0.3.1, one commit. Everything the release ships is already on
mainin #152; this moves the version and cuts the notes.pyproject.toml,src/agentseam/__init__.pyandCITATION.cff→ 0.3.1.tests/test_repo_standards.pyholds the last two to the package, so a bump that forgot either fails the suite.CHANGELOG.md:## [Unreleased]becomes## [0.3.1] - 2026-09-20and its compare link becomes the 0.3.1 link. No empty Unreleased heading above it:release.ymlextracts the first section as the notes.docs/assets/social-preview.{svg,png}regenerated withgen_brand_assets.py: the card prints the version, and thebrand-assetsjob checks it.Why a patch and not 0.4.0. #152 is seven fixes and no new module, data or public name. The one behaviour change (a handler that raises is refused in dialect rather than crashing to a non-blocking error) closes a fail-open path; chock's own bundle wrap already assumed it.
The tag that already exists
v0.3.1was pushed at486fea7, the #152 merge, where the version is still 0.3.0. The Release run on that tag (run 35541952032) built anagentseam-0.3.0wheel and failed at the PyPI upload, so nothing was published. After this merges, delete that tag and re-pushv0.3.1at the merge commit:Then chock bumps its pin to 0.3.1 and regenerates its vendored runtimes before its 0.9.1 tag.
Verification
🤖 Generated with Claude Code