Repository navigation
CodeQL: move to action v4 before the deprecated v2 is retired - #1259
Conversation
Hello jeanmarcmilletscality,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: |
ℹ️ No review performedNo test review was performed: no code under test could be determined: the pull request changes no code and no tests. |
|
|
||
| - name: Initialize CodeQL | ||
| uses: github/codeql-action/init@v2 | ||
| uses: github/codeql-action/init@v3 |
There was a problem hiding this comment.
v3 is not the current major: GitHub shipped CodeQL Action v4 (Node 24) in October 2025 and has said v3 will be deprecated in December 2026, which is two months away. Go straight to v4 so this change doesn't have to be made again.
| uses: github/codeql-action/init@v3 | |
| uses: github/codeql-action/init@v4 |
|
|
||
| - name: Build and analyze | ||
| uses: github/codeql-action/analyze@v2 | ||
| uses: github/codeql-action/analyze@v3 |
There was a problem hiding this comment.
Same as init: pin analyze to v4 so both steps stay on the same major.
| uses: github/codeql-action/analyze@v3 | |
| uses: github/codeql-action/analyze@v4 |
v3 is not the landing place: it is already announced for deprecation in December 2026, and GitHub has been cutting both majors on the same day since v4 shipped. v4 runs on node24, which the hosted ubuntu runners provide.
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: |
|
/approve |
|
I have successfully merged the changeset of this pull request
Please check the status of the associated issue None. Goodbye jeanmarcmilletscality. The following options are set: approve |
TL;DR — The CodeQL workflow still pins the action major GitHub has deprecated; this moves it to v4 before v2 stops running.
Context / Why
Every CodeQL run in this repo logs an error annotation from GitHub:
Nothing is red today — GitHub annotates but still runs v2, and the recent runs on
development/1.0are green. It turns into a hard failure when v2 is actually retired, and the fix is the same two lines either way.The annotation asks for v3, but v3 is not where this should land: it is already announced for deprecation in December 2026, and GitHub now cuts both majors on the same day (v4.39.0 and v3.39.0 both went out on 15 October 2026). v4 is the current major and runs on
node24, which the hostedubuntu-latestrunners provide.🧩 Approach
codeql.yamlis the only file in the repo pinning a CodeQL action; the other six workflows are already on current majors.🧪 How to test
The workflow runs on this PR. Open the Static analysis with CodeQL check and confirm two things: the deprecation annotation is gone from Initialize CodeQL, and the analysis still completes and uploads its results, with the job's conclusion staying
success.