From a059a7a0ee19212a3820398327f1ba34fd73676f Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 12 Dec 2024 20:29:38 +0000 Subject: [PATCH 1/4] Update changelog and version after v3.27.8 --- CHANGELOG.md | 4 ++++ package-lock.json | 4 ++-- package.json | 2 +- 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index afda07ee33..22653e7d88 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -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. +## [UNRELEASED] + +No user facing changes. + ## 3.27.8 - 12 Dec 2024 - 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) diff --git a/package-lock.json b/package-lock.json index deadc92422..376d919f39 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "codeql", - "version": "3.27.8", + "version": "3.27.9", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "codeql", - "version": "3.27.8", + "version": "3.27.9", "license": "MIT", "dependencies": { "@actions/artifact": "^2.1.9", diff --git a/package.json b/package.json index e2a94c281a..362e7e605b 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "codeql", - "version": "3.27.8", + "version": "3.27.9", "private": true, "description": "CodeQL action", "scripts": { From 92753708cf0395732c3e3ea1666edb55192158c5 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 12 Dec 2024 20:50:20 +0000 Subject: [PATCH 2/4] Update checked-in dependencies --- node_modules/.package-lock.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/node_modules/.package-lock.json b/node_modules/.package-lock.json index 027d71e7ee..009fde807f 100644 --- a/node_modules/.package-lock.json +++ b/node_modules/.package-lock.json @@ -1,6 +1,6 @@ { "name": "codeql", - "version": "3.27.8", + "version": "3.27.9", "lockfileVersion": 3, "requires": true, "packages": { From f124ad0e7ef6ecb9840fcd1b908d1630211d37c3 Mon Sep 17 00:00:00 2001 From: Andrew Eisenberg Date: Thu, 12 Dec 2024 12:46:04 -0800 Subject: [PATCH 3/4] Adds an environment for creating releases The `app-id` is only available in the `Automation` environment. --- .github/workflows/post-release-mergeback.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/post-release-mergeback.yml b/.github/workflows/post-release-mergeback.yml index d6ac0a35f5..e94352c200 100644 --- a/.github/workflows/post-release-mergeback.yml +++ b/.github/workflows/post-release-mergeback.yml @@ -21,6 +21,7 @@ on: jobs: merge-back: runs-on: ubuntu-latest + environment: Automation if: github.repository == 'github/codeql-action' env: BASE_BRANCH: "${{ github.event.inputs.baseBranch || 'main' }}" From feca44ddf6862ba0707723d320d5c42780fe6499 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 12 Dec 2024 22:36:29 +0000 Subject: [PATCH 4/4] Update changelog for v3.27.9 --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 22653e7d88..0de71e9b2f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,7 +4,7 @@ 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. -## [UNRELEASED] +## 3.27.9 - 12 Dec 2024 No user facing changes.