FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

docs: guidance on keeping the CodeQL Action up to date by sam-robson · Pull Request #3499 · github/codeql-action · GitHub

docs: guidance on keeping the CodeQL Action up to date - #3499

Merged
sam-robson merged 2 commits into
mainfrom
sam-robson/document-version-pinning-risk
Feb 23, 2026
Merged

docs: guidance on keeping the CodeQL Action up to date#3499
sam-robson merged 2 commits into
mainfrom
sam-robson/document-version-pinning-risk

Conversation

Copy link
Copy Markdown
Contributor

Summary

  • Document the recommendation to use major version tags when referencing the CodeQL Action
  • Note that pinned versions should be kept updated to avoid losing functionality from server-side feature flag changes

Copilot AI review requested due to automatic review settings February 20, 2026 20:33
sam-robson requested a review from a team as a code owner February 20, 2026 20:33

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Pull request overview

This PR adds documentation to the README about keeping the CodeQL Action up to date. The new section provides guidance on version pinning strategies and warns about potential functionality loss when using pinned versions with server-side feature flag changes.

Changes:

  • Added a new "Keeping the CodeQL Action up to date" section to README.md
  • Documented the recommendation to use major version tags (e.g., v3) for automatic updates
  • Added guidance for users who pin to specific commit SHAs or patch versions
  • Explained that server-side feature flags may be removed over time, affecting pinned versions

redsun82 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

LGTM!

sam-robson added the size/XS Should be very easy to review label Feb 23, 2026
sam-robson enabled auto-merge February 23, 2026 10:07
sam-robson merged commit 4ea06e9 into main Feb 23, 2026
254 checks passed
sam-robson deleted the sam-robson/document-version-pinning-risk branch February 23, 2026 10:34

mbg 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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Sorry, @redsun82 beat me to this, but just a couple of comments. Let's also discuss this a bit more on the internal issue.

I'll open a PR for the v3=>v4 change.

Comment thread README.md

## Keeping the CodeQL Action up to date

We recommend referencing the CodeQL Action using a major version tag (e.g. `v3`) in your workflow file. This ensures your workflow automatically picks up the latest release within that major version, including bug fixes, new features, and updated CodeQL CLI versions.

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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

This should be v4 now.

Comment thread README.md

If you pin to a specific commit SHA or patch version tag, ensure you keep it updated (e.g. via [Dependabot](https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot)). Some CodeQL Action features are controlled by server-side flags that may be removed over time, which can cause pinned versions to lose functionality.


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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Minor: extra empty line?

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/XS Should be very easy to review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants


Back | FazBrowse Home | New Git URL