-name:Generate token

uses:actions/create-github-app-token@5d869da34e18e7287c1daad50e0b8ea0f506ce69

id:app-token

with:

app-id:${{ vars.AUTOMATION_APP_ID }}

private-key:${{ secrets.AUTOMATION_PRIVATE_KEY }}

-name:Create the GitHub release

env:

PARTIAL_CHANGELOG:"${{ runner.temp }}/partial_changelog.md"

VERSION:"${{ steps.getVersion.outputs.version }}"

GH_TOKEN:${{secrets.GITHUB_TOKEN }}

GH_TOKEN:${{steps.app-token.outputs.token }}

run:|

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.

- Fixed an issue where streaming the download and extraction of the CodeQL bundle did not respect proxy settings.[#2624](https://github.com/github/codeql-action/pull/2624)

- We are rolling out a change in December 2024 that will extract the CodeQL bundle directly to the toolcache to improve performance.[#2631](https://github.com/github/codeql-action/pull/2631)