build(deps): bump toml from 1.1.5+spec-1.1.0 to 1.1.6+spec-1.1.0 in /cli

[dependabot]

Bumps toml from 1.1.5+spec-1.1.0 to 1.1.6+spec-1.1.0.

Commits

• 572c005 chore: Release
• 66d0c53 docs: Update changelog
• 07af4e7 perf: Reduce allocations in toml_edit parsing and dumping (#1215)
• 0ff90db perf(display): Write encoded strings directly
• efb2536 perf(display): Move generated representation strings
• 075c444 refactor(display): Consolidate key-path encoding
• b48f338 perf(display): Borrow table keys during document output
• c6c1de3 perf(parser): Move completed table header keys
• ec90463 perf(parser): Borrow input when creating editable documents
• d76a48a test: Benchmark rendering generated keys and values
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[skymanbp]

Closing: this repository's Dependabot version-update lanes are parked as of d80f1f9 — .github/dependabot.yml now carries open-pull-requests-limit: 0 on all three lanes, so version updates open nothing on a schedule. Security updates are a separate channel and are not affected by that limit; those still arrive.

Nothing is wrong with this bump. The reason it is not being merged is that cli/Cargo.lock is a measured build input: the bench joining rule treats a lock change as a new program (see docs/BENCH.md), so merging a patch-level dependency bump obliges a fresh measurement run and a release to carry it. That is the right trade while a project is being actively developed, and the wrong one now that this one is in maintenance.

To take this upgrade on purpose later: raise open-pull-requests-limit on the cargo lane, let the scheduled run re-open the PR, merge it, then set the limit back to 0.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.