github
diff --git a/‎CHANGELOG.md
Lines changed: 4 additions & 0 deletions b/‎CHANGELOG.md
Lines changed: 4 additions & 0 deletions
diff --git a/‎init/action.yml
Lines changed: 1 addition & 1 deletion b/‎init/action.yml
Lines changed: 1 addition & 1 deletion
diff --git a/‎lib/analyze.js
Lines changed: 1 addition & 1 deletion b/‎lib/analyze.js
Lines changed: 1 addition & 1 deletion
diff --git a/‎lib/analyze.js.map
Lines changed: 1 addition & 1 deletion b/‎lib/analyze.js.map
Lines changed: 1 addition & 1 deletion
diff --git a/‎lib/autobuild.js
Lines changed: 1 addition & 1 deletion b/‎lib/autobuild.js
Lines changed: 1 addition & 1 deletion
diff --git a/‎lib/autobuild.js.map
Lines changed: 1 addition & 1 deletion b/‎lib/autobuild.js.map
Lines changed: 1 addition & 1 deletion
diff --git a/‎lib/cli-errors.js
Lines changed: 51 additions & 10 deletions b/‎lib/cli-errors.js
Lines changed: 51 additions & 10 deletions
@@ -4,6 +4,10 @@ See the [releases page](https://github.com/github/codeql-action/releases) for th
 
 Note that the only difference between `v2` and `v3` of the CodeQL Action is the node version they support, with `v3` running on node 20 while we continue to release `v2` to support running on node 16. For example `3.22.11` was the first `v3` release and is functionally identical to `2.22.11`. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
 
+## 3.24.8 - 18 Mar 2024
+
+- Improve the ease of debugging extraction issues by increasing the verbosity of the extractor logs when running in debug mode. [#2195](https://github.com/github/codeql-action/pull/2195)
+
 ## 3.24.7 - 12 Mar 2024
 
 - Update default CodeQL bundle version to 2.16.4. [#2185](https://github.com/github/codeql-action/pull/2185)
 
@@ -78,7 +78,7 @@ inputs:
     required: false
   packs:
     description: >-
-      [Experimental] Comma-separated list of packs to run. Reference a pack in the format `scope/name[@version]`. If `version` is not
+      Comma-separated list of packs to run. Reference a pack in the format `scope/name[@version]`. If `version` is not
       specified, then the latest version of the pack is used. By default, this overrides the same setting in a
       configuration file; prefix with "+" to use both sets of packs.