Skip to content

clang-tidy: bump default and known_good_version to 20.1.0 - #1139

Open
helly25 wants to merge 2 commits into
trunk-io:mainfrom
helly25:clang-tidy-default-20.1.0
Open

clang-tidy: bump default and known_good_version to 20.1.0#1139
helly25 wants to merge 2 commits into
trunk-io:mainfrom
helly25:clang-tidy-default-20.1.0

Conversation

@helly25

@helly25 helly25 commented May 16, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Move clang-tidy's default version from 15.0.6 and both known_good_version fields from 16.0.3 to 20.1.0, the newest patch the trunk.io CDN actually hosts.
  • Add a header comment in plugin.yaml enumerating the patches available per platform on the trunk.io CDN.

Parallel to #1138 (clang-format). The downloads: block is structurally unchanged — only the default and the documented known_good_versions move.

Test plan

  • Pre-push hook runs tests/repo_tests/{valid_package_download,config_check}.test.ts — passed.
  • CI: bumping the linter major may change diagnostic output across existing test fixtures; reviewers should check the clang-tidy snapshot tests.

🤖 Generated with Claude Code

helly25 and others added 2 commits May 16, 2026 22:09
Document the patch versions trunk.io's CDN actually publishes for
clang-tidy and move the defaults from 15.0.6 / 16.0.3 to 20.1.0,
which is the newest patch available across all four platforms.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

@EliSchleifer EliSchleifer left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@trunk-io

trunk-io Bot commented Aug 1, 2026

Copy link
Copy Markdown

❌ This pull request was removed from the merge queue because it failed tests. PR #1157 was used for testing. See more details here.

Failed Required Status Conclusion
Aggregate Test Results Failure
  • 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.

2 participants