Skip to content

Bump toml from 0.8 to 0.9#1346

Open
glamberson wants to merge 1 commit into
XAMPPRocky:masterfrom
lamco-admin:bump-toml-0.9
Open

Bump toml from 0.8 to 0.9#1346
glamberson wants to merge 1 commit into
XAMPPRocky:masterfrom
lamco-admin:bump-toml-0.9

Conversation

@glamberson
Copy link
Copy Markdown

Bumps toml from 0.8.19 to 0.9 (stable since 2025-08-29).

The single call site is src/config.rs:68, which uses toml::from_str(&s).ok(). That API is stable across 0.8 and 0.9, so no source changes are required.

MSRV

toml 0.9.0's MSRV is 1.66, well under tokei's current rust-version = "1.71". No MSRV impact.

Verification

  • cargo build: clean
  • cargo test: 22 passed, 0 failed
  • cargo fmt --all --check: clean

Note: cargo clippy --all-targets -- -D warnings currently fails with 7 pre-existing errors on master (reproducible on vanilla master before this change). CI does not run clippy, so this bump does not affect CI results.

Lockfile

cargo update --package toml --precise 0.9.11 produced the 90-line lockfile diff. Most of the churn is adding toml_writer 1.1.1 and splitting winnow (the toml 0.9 stack depends on winnow 0.7 in some places and winnow 1.0 in others). This matches what every consumer of toml 0.9 will see.

Context

The bump is part of the Debian Rust team's toml 0.9 transition (tracked at debcargo-conf#147). tokei is one of the reverse-dependencies currently on 0.8; merging this removes it from the transition list.

toml 0.9 has been stable on crates.io since 2025-08-29. The single
call site in this crate (src/config.rs:68) uses toml::from_str,
which is stable across 0.8 and 0.9. No source changes required.

toml 0.9's MSRV is 1.66, well under tokei's rust-version = "1.71".

Verified:
  cargo build
  cargo test            (22 passed, 0 failed)
  cargo fmt --all --check

Note: cargo clippy on master currently fails with 7 pre-existing
errors (unrelated to this change; reproduce with
git stash && cargo clippy --all-targets -- -D warnings).
CI does not run clippy, so this change does not affect CI results.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant