From bce7dc4616e20ab1756093d4b2da5902a12d1617 Mon Sep 17 00:00:00 2001 From: "Michael B. Gale" Date: Mon, 23 Feb 2026 11:58:25 +0000 Subject: [PATCH] `v3` => `v4` --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 03db318f1..8d830a05f 100644 --- a/README.md +++ b/README.md @@ -82,7 +82,7 @@ See the full list of GHES release and deprecation dates at [GitHub Enterprise Se ## 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. +We recommend referencing the CodeQL Action using a major version tag (e.g. `v4`) 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. 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.