[Github] Bump clang-format to 21.1.0 #155660
Conversation
This patch bumps the clang-format version in the pr-code-format action to the latest release version, in line with how we have handled this before.
|
@llvm/pr-subscribers-github-workflow Author: Aiden Grossman (boomanaiden154) ChangesThis patch bumps the clang-format version in the pr-code-format action to the latest release version, in line with how we have handled this before. Full diff: https://github.com/llvm/llvm-project/pull/155660.diff 1 Files Affected:
diff --git a/.github/workflows/pr-code-format.yml b/.github/workflows/pr-code-format.yml
index 5540555ae05ed..3089debbdbc2f 100644
--- a/.github/workflows/pr-code-format.yml
+++ b/.github/workflows/pr-code-format.yml
@@ -55,7 +55,7 @@ jobs:
- name: Install clang-format
uses: aminya/setup-cpp@17c11551771948abc5752bbf3183482567c7caf0 # v1.1.1
with:
- clangformat: 20.1.8
+ clangformat: 21.1.0
- name: Setup Python env
uses: actions/setup-python@42375524e23c412d93fb67b49958b491fce71c38 # v5.4.0
|
|
Should we wait until #155466 is merged? |
That's only needed for the reproduction instructions. We're not actually using it in the CI. The way the git history gets setup in the CI is quite a bit different than it typically is locally due to how Github handles things. |
|
So are we updating the clang-format version twice for each release cycle? See #141819 (comment). |
Sounds reasonable enough to me. In the comment I also mentioned we should upgrade if there are relevant |
This patch bumps the clang-format version in the pr-code-format action to the latest release version, in line with how we have handled this before.