Update Rust crates and Python dev dependency floors - #55
Merged
Conversation
Rust: cargo update for semver-compatible bumps, plus toml 0.8->1.1, criterion 0.5->0.8, and the ruff_python_* git dependencies from tag 0.15.0 to 0.16.2. Verified with cargo build/test/clippy/fmt. Python: bump dev/docs dependency-group floors to current releases (mypy 2.x, pyrefly 1.x, invoke 3.x, pyarrow 25.x, mkdocstrings-python 2.x, ruff 0.16.x, etc.). licensecheck was left at 2025.1.0 since 2026.x requires Python >=3.12, which conflicts with this project's >=3.11 floor. The optional-dependencies floors (pandas/pandera/polars, the library's own supported-version promises to users) are intentionally untouched. ruff 0.16 enables ~7x more default rules (added CPY001 to the ignore list, since this project doesn't use copyright headers) and now formats Python code blocks embedded in Markdown by default, which reformatted 17 docs/example files. Verified: cargo test/clippy, ruff check/format, ty check, mypy plugin tests, bandit, complexipy, pip-audit, and the full pytest + coverage suite all pass.
benches/parser_bench.rs is at rust/benches/, so reaching examples/features/typedframes_example.py at the repo root only needs two ../ segments, not three. The extra segment made cargo build --benches (and cargo bench) fail unconditionally on main.
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.
Summary
cargo updatefor semver-compatible bumps, plus major bumps fortoml(0.8→1.1),criterion(0.5→0.8), and theruff_python_*git dependencies (tag0.15.0→0.16.2, the internal ruff crates this checker's parser is built on).dev/docsdependency-group floors to current releases, including major jumps (mypy 1→2, pyrefly 0.x→1.x, invoke 2→3, complexipy 5→6, pyarrow 23→25, mkdocstrings-python 1→2).licensecheckstayed at 2025.1.0 since the 2026.x series requires Python ≥3.12, which conflicts with this project's>=3.11floor. Theoptional-dependenciesfloors (pandas,pandera,polars— this library's own supported-version promise to its users) were deliberately left alone, since that's a compatibility policy decision separate from dev-tooling freshness.CPY001(copyright-header) to the ignore list since this project has never used copyright headers.rust/benches/parser_bench.rshad one extra../in itsinclude_str!path, socargo build --benches/cargo benchfailed unconditionally onmain.Test plan
cargo build/cargo test(154 tests) /cargo clippy -- -D warnings/cargo fmt --check/cargo bench(now compiles and runs)ruff check ./ruff format --check ./ty check .bandit,complexipy,pip-audit(no known vulnerabilities)mkdocs build --strictpytestsuite (299 tests) + coverage threshold, including the mypy-plugin tests against mypy 2.x