bump deps - #7
Merged
Merged
Conversation
- pyo3 0.28 -> 0.29 - ruff git rev 9b03f2b2 -> fbe3e251 - cargo update for the rest of the tree - re-pin CI actions: checkout v7.0.1, setup-python v7.0.0, attest v4.2.2, setup-uv v9.0.0 - regenerate CI.yml header from maturin 1.14.1 (template output otherwise unchanged) - version 0.5.2 -> 0.5.4 (0.5.3 tag exists but never published)
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.
Rust deps
#[pymodule(gil_used = false)],Bound, and the#[pyo3(signature = ...)]attr all compile unchanged.9b03f2b2→fbe3e251(ruff_python_formatter/ruff_python_parser, crate versions 0.0.1 → 0.0.8).cargo updateon the rest of the tree. Notable:zip0.6.6 → 8.6.0,wasm-bindgen0.2.118 → 0.2.127,thiserror2.0.18 → 2.0.20,zerocopy0.8.48 → 0.8.56. The lock shrinks a fair bit (droppedwit-bindgen/wasm-*andserde_with).CI
Re-pinned to the latest release SHAs:
actions/checkoutv6.0.2 → v7.0.1actions/setup-pythonv6.2.0 → v7.0.0actions/attestv4.1.0 → v4.2.2astral-sh/setup-uvv8.1.0 → v9.0.0download-artifactv8.0.1,upload-artifactv7.0.1 andmaturin-actionv1.51.0 were already current.Two checks on the major bumps: setup-python v7 drops the
pip-installinput (unused here) and its "remove EOL Python versions" change only touched their own test workflows, sopython-version: "3.8"still resolves. setup-uv v9 flipsprune-cachetofalseby default — a cache-size change, not a behavior break.I also regenerated the workflow from the maturin template to check for drift. maturin 1.14.1 emits a byte-identical template to 1.13.3 for this project, and our file already matches it apart from two deliberate local customizations, both preserved: the SHA pins (vs the template's floating
@v6/@v1tags) and the omittedUV_PUBLISH_TOKENenv (we use PyPI trusted publishing viaid-token: write). So the only change here is the header comment, now v1.14.1.Version: 0.5.2 → 0.5.4
Skipping 0.5.3 deliberately. The
v0.5.3tag already exists on c6823b0, but that release never made it to PyPI — latest there is 0.5.2. Cargo.toml wasn't bumped in that commit, so the tagged build produced another 0.5.2 and PyPI would have rejected it as a duplicate. Reusing 0.5.3 now would collide with the existing tag, so 0.5.4 is the next clean number. Patch bump matches the precedent from #4, the previous deps bump.Test plan
cargo buildclean on pyo3 0.29 + the new ruff rev.maturin develop+ smoke test:format_string, theline_width=kwarg, andis_valid_syntaxall behave correctly.