Skip to content

Update toml-tidy to 0.7.0 - #1190

Open
AndrewDongminYoo wants to merge 1 commit into
trunk-io:mainfrom
AndrewDongminYoo:toml-tidy-0.7.0
Open

AndrewDongminYoo wants to merge 1 commit into
trunk-io:mainfrom
AndrewDongminYoo:toml-tidy-0.7.0

Conversation

@AndrewDongminYoo

Copy link
Copy Markdown
Contributor

Bumps known_good_version for toml-tidy from 0.3.1 to 0.7.0, renames the fmt snapshot accordingly, and declares the standalone configuration files that 0.7.0 reads.

What is new upstream

  • 0.7.0 reads its settings from .toml-tidy.toml and toml-tidy.toml as well as [tool.toml-tidy] in pyproject.toml, with Ruff-style discovery (the closest file above each target applies). Repositories without a pyproject.toml can now configure it under Trunk. The definition lists both files in direct_configs, the same shape as ruff's direct_configs: [ruff.toml], and keeps pyproject.toml in affects_cache.
  • 0.7.0 also adds --order version and --diff, and its own pre-commit hook no longer touches lockfiles.
  • 0.4.x made --in-place writes atomic; 0.5.0 and 0.6.0 normalize the spacing of single-line arrays by default and add an opt-in --line-width.

The command this plugin runs (toml-tidy --in-place ${target}) is unchanged.
The fixture has no arrays, so the snapshot content is byte-identical to the 0.3.1 one and only the version in its filename changed (git diff -M reports the rename as 100% similarity).
The README now names 0.7.0 and the new configuration files.

Verification

PLUGINS_TEST_LINTER_VERSION=KnownGoodVersion npx jest linters/toml-tidy --ci → 1 test passed, 1 snapshot passed against the renamed toml_tidy_v0.7.0_basic.fmt.shot.
As a hermeticity check, PLUGINS_TEST_LINTER_VERSION=0.99.0 fails with a task failure, so the test installs the pinned version rather than a toml-tidy already on PATH.

@trunk-io

trunk-io Bot commented Oct 26, 2026

Copy link
Copy Markdown

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant