build(deps): llm-tokenizer's toml entry in Cargo.lock names the locked 1.1.6

[hello-alexmcc]

Description

Problem

main's Cargo.lock fails --locked: cargo metadata --locked exits 101. #2829 moved toml to 1.1.6. #2817, merged after it, added toml to llm-tokenizer's dev-dependencies, and its lock entry still names toml 1.1.5+spec-1.1.0, which the lock no longer holds. A build without --locked silently rewrites the lock, so CI does not see it.

Solution

llm-tokenizer's dependency entry names the locked toml 1.1.6+spec-1.1.0.

Changes

• Cargo.lock: one line.

Test Plan

• On main 200ed03: cargo +1.98.0 metadata --locked --format-version 1 exits 101.
• On this branch: the same command exits 0, and no toml 1.1.5 entry is left.

Checklist

• cargo +nightly fmt passes
• cargo clippy --all-targets --all-features -- -D warnings passes
• (Optional) Documentation updated
• (Optional) Please join us on Slack #sig-smg to discuss, review, and merge PRs

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Team
• Run ID: 102c7bd7-510a-4233-8b51-f0caee1b6b5a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}