chore(release): prepare v0.5.0 - #85
Merged
Merged
Conversation
Move the stream-reset entry from [Unreleased] into 0.5.0 and bump the version. Minor rather than patch: it adds a feature, and `AbstractBackend` gains five abstract methods, which an out-of-tree backend subclass would have to implement. Split the changelog entry into several bullets. publish.yml lifts this section verbatim into the GitHub Release body, and it was one ~1900 character paragraph. Co-Authored-By: Claude <noreply@anthropic.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
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.
Release prep for v0.5.0, following #84.
CHANGELOG.md—[Unreleased]→## [0.5.0] - 2026-08-06pyproject.toml+uv.lock—0.4.1→0.5.0Minor, not patch: it adds a feature, and
AbstractBackendgains five abstract methods that an out-of-tree backend subclass would have to implement. Called out under### Changedso it isn't a surprise.I also split the changelog entry into several bullets —
publish.ymllifts this section verbatim into the GitHub Release body, and it was a single ~1900-character paragraph.Checked before committing
awkfrompublish.ymlagainst the edited file: 2352 bytes, stops cleanly before the 0.4.1 section (no bleed-through). Without this the workflow silently falls back to a bare"Release 0.5.0"body.uv build→bizon-0.5.0.tar.gz+bizon-0.5.0-py3-none-any.whl.bizon stream reset, the--streamoption, and theStreamResetmodel are all present in the built artifact rather than assuming the build picked them up.After merge
git tag v0.5.0 && git push origin v0.5.0firespublish.yml: build → PyPI → GitHub Release. That step is irreversible, so I'll leave the tag to you unless you'd rather I push it.🤖 Generated with Claude Code