chore(release): bump versions and cut CHANGELOG v0.5.0 wave#159
Merged
Conversation
Prepare the v0.5.0 release. Bump the 8 packages carrying unreleased changes and refresh the umbrella floors: core 0.3.5->0.3.6, cli 0.3.3->0.3.4, s3 0.3.4->0.3.5, google 0.3.1->0.3.2, replicate 0.3.2->0.3.3, openai 0.3.1->0.3.2, gmicloud 0.3.2->0.3.3, umbrella 0.4.2->0.4.3. CHANGELOG: fold the two mis-sectioned entries (PromptTemplate #88 into genblaze-core, gmicloud duration #90 into genblaze-gmicloud), add the missing genblaze-s3 entry for the widened aioboto3 pin (#128), update the umbrella note, and cut [Unreleased] to the dated [0.5.0] wave header with a Released package versions list. core stays on 0.3.6, not 0.4.0 — that version is reserved in-code for the raise_on_failure default flip and probe_model() removal. The s3 bump clears the pin-parity gate: #128 widened its aioboto3 pin at an already-published version (0.3.4), which the gate flags until republished under a new version. No source/behavior changes — release bookkeeping only. Tag as v0.5.0 after merge (the release workflow validates the tag against this header).
test_cli_core_dependency_floor_matches_local_core asserts the CLI's genblaze-core pin matches the local core version, which this wave bumped to 0.3.6. The umbrella floor was already updated; the CLI's was missed.
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.
Release bookkeeping for v0.5.0
Pure bookkeeping — no source or behavior changes. Prepares the merged fix wave (#138–#156) to be tagged and published.
Version bumps (8)
genblaze-coreraise_on_failureflip /probe_model()removalgenblaze-cligenblaze-s3pin-parity(widenedaioboto3pin from #128)genblaze-googlegenblaze-replicategenblaze-openaigenblaze-gmicloudgenblaze(umbrella)>=0.3.6, s3>=0.3.5, gmicloud/google/openai/replicate extrasOther connectors are untouched — their
genblaze-core>=0.3.4,<0.4floor already admits 0.3.6, so they don't need republishing.CHANGELOG
### Security) →genblaze-core; gmicloud duration GMICloud video duration=int coercer silently truncates fractional seconds #90 (was under a bare### Changed) →genblaze-gmicloud.### genblaze-s3entry for the widenedaioboto3pin (chore(deps): apply dependabot updates #128).[Unreleased]→## [0.5.0] - 2026-07-16with aReleased package versionslist.Verification
[Unreleased]is empty →changelog-gatepasses.## [0.5.0]→validate-versionwill require tagv0.5.0.ruff check/ruff format --checkclean.After merge (release steps — your call)
make pre-releasein a full env (localtwinewas missing here).git tag -a v0.5.0 -m "Release 0.5.0"&& push the tag.v0.5.0using the[0.5.0]CHANGELOG slice as the body — this fires.github/workflows/release.yml.Refs #128 #88 #90