chore(release): prepare v0.5.1 - #87
Merged
Merged
Conversation
Patch release for the bare-install ImportError: 0.5.0 ships a CLI that cannot start without the `bigquery` extra. 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.
Patch release for #86. 0.5.0 ships a CLI that cannot start without the
bigqueryextra, so this should go out promptly.CHANGELOG.md— new## [0.5.1] - 2026-08-06under### Fixedpyproject.toml+uv.lock—0.5.0→0.5.1Patch rather than minor: no API change, no new behaviour, just a broken import path made lazy.
Checked before committing
awkfrompublish.yml: 804 bytes, no bleed into the 0.5.0 section. Without this the workflow silently falls back to a bare"Release 0.5.1"body.uv buildsucceeds →bizon-0.5.1.tar.gz+bizon-0.5.1-py3-none-any.whl.resolve_default_table_idwith nothing at module level.google.cloud.bigqueryabsent) and ranbizon --helpsuccessfully. This is the check that would have caught the problem before 0.5.0 went out.After merge
git tag v0.5.1 && git push origin v0.5.1→ build → PyPI → GitHub Release. Irreversible, so I'll leave the tag to you unless you'd rather I push it.🤖 Generated with Claude Code