Repository navigation
chore(release): bump version to 0.4.2 - #33
Merged
Merged
Conversation
The v0.4.1 tag was cut without bumping the package version, so CD built every artifact as 0.4.0. Both registries already hold 0.4.0, and both publish steps failed on the duplicate: PyPI returned 400 Bad Request and cargo publish exited 101 with "already exists on crates.io index". v0.4.1 stays where it is as a release that did not publish. 0.4.2 carries the same code out to both registries instead. python/pyproject.toml declares dynamic = ["version"], so the wheel version comes from python/Cargo.toml; the crates.io release version comes from core/Cargo.toml. Both need the bump. Assisted-by: ClaudeCode:claude-opus-5
This was referenced Aug 13, 2026
Merging this PR will not alter performance
Comparing 
Footnotes
|
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.
🤖 AI text below 🤖
The
v0.4.1tag was cut without bumping the package version, so the CD run built every artifact as0.4.0. Both registries already hold0.4.0, and both publish steps failed on the duplicate:ERROR HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/, on the first file (cast_value_rs-0.4.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl). The 120 files for 0.4.0 were uploaded on 2026-04-01.error: crate zarr-cast-value@0.4.0 already exists on crates.io index, exit 101. The job still reported green because the step carriescontinue-on-error: true; that is fixed in ci: fail the crates.io job when publishing actually fails #30.Nothing was wrong with the builds, trusted publishing, or the Sigstore attestations.
v0.4.1is left untouched — a release that was cut and did not publish. This bumps to0.4.2so the same code ships under a version that was never taken.Two files need the bump, because the two registries read the version from different places:
core/Cargo.toml— whatcargo publish -p zarr-cast-valuereleases.python/Cargo.toml—python/pyproject.tomldeclaresdynamic = ["version"], so maturin stamps the wheel version from here.Cargo.lockis regenerated to match. No other file in the repo pins the version.After merging
Tag the merge commit
v0.4.2to trigger CD.Testing
cargo test --workspacepasses (50 tests).