Sourced from gradle/actions's releases.
v6.2.0
Highlights
This release brings significant behaviour improvements to Enhanced caching, improvements to the generated Job Summary, and a number of correctness and security fixes.
- Improved cache-cleanup mechanism. Cleanup of stale files from the Gradle User Home is now faster, and no longer depends on Gradle or a JVM. It works by inspecting the local file state directly, removing the Gradle invocation from the post-build step.
- More granular, more stable caching. The local build cache is stored as a separate cache entry, so it can be restored and invalidated independently of the main Gradle User Home entry. Transient Gradle housekeeping files are excluded from the cache, reducing its size and improving stability.
- Hide obsolete Job summaries in PR commments: When a new Job summary comment is added to a PR, previous outdated Job summaries are now hidden.
- Improved caching report in the job summary. The cache report now uses a single, consistent layout across all cache states and providers. Provider information is integrated directly into the report, and per-entry details are available in an expandable section. (#985)
- Correctness and security fixes. A unique cache key is now used per run attempt, so re-runs no longer collide; the job summary shows the cache key string rather than an internal id; and bundled dependencies have been updated, including a ReDoS fix and a fast-xml CVE fix.
What's Changed
- Remove unnecessary dependency overrides by
@bigdazin gradle/actions#981- Scope CI-integ-test concurrency groups per-branch by
@bigdazin gradle/actions#983- Improve typings by
@Vampirein gradle/actions#938- Hide obsolete Job summaries by
@SimonMarquisin gradle/actions#902- CI: add requireable aggregate/no-op checks for branch protection by
@bigdazin gradle/actions#984- Redesign the caching Job Summary by
@bigdazin gradle/actions#985New Contributors
@Vampiremade their first contribution in gradle/actions#938Full Changelog: https://github.com/gradle/actions/compare/v6.1.1...v6.2.0
v6.1.1
This release updates various dependency versions, resolving several reported security vulnerabilities. No functional changes are included
What's Changed
- Bump Gradle Wrapper from 9.4.1 to 9.5.1 in /sources/test/init-scripts by
@bot-githubactionin gradle/actions#961- Bump Gradle Wrapper from 9.4.1 to 9.5.1 in /.github/workflow-samples/gradle-plugin by
@bot-githubactionin gradle/actions#962- Bump Gradle Wrapper from 9.4.1 to 9.5.1 in /.github/workflow-samples/groovy-dsl by
@bot-githubactionin gradle/actions#963- Bump Gradle Wrapper from 9.4.1 to 9.5.1 in /.github/workflow-samples/java-toolchain by
@bot-githubactionin gradle/actions#964- Bump Gradle Wrapper from 9.4.1 to 9.5.1 in /.github/workflow-samples/kotlin-dsl by
@bot-githubactionin gradle/actions#965- Update known wrapper checksums by
@github-actions[bot] in gradle/actions#937- Bump the github-actions group across 2 directories with 8 updates by
@dependabot[bot] in gradle/actions#976- Bump the npm-dependencies group across 1 directory with 14 updates by
@dependabot[bot] in gradle/actions#970- Bump references to Develocity Gradle plugin from 4.4.0 to 4.4.2 by
@bot-githubactionin gradle/actions#973- Bump the npm-dependencies group in /sources with 5 updates by
@dependabot[bot] in gradle/actions#977- Update
@actions/cacheand@actions/artifact, stop ignoring them in Dependabot by@bigdazin gradle/actions#978- Resolve npm security vulnerabilities via dependency overrides by
@bigdazin gradle/actions#980Full Changelog: https://github.com/gradle/actions/compare/v6.1.0...v6.1.1
v6.1.0
New: Basic Cache Provider
A new MIT-licensed Basic Caching provider is now available as an alternative to the proprietary Enhanced Caching provided by
gradle-actions-caching. Choose Basic Caching by settingcache-provider: basiconsetup-gradleordependency-submissionactions.
- Built on
@actions/cache-- fully open source
... (truncated)
b6eebf3
[bot] Update dist directory9901393
Remove unnecessary dependency overrides (#981)20ce680
Update RELEASING.md5e2ebd0
[bot] Update dist directory9e2c1cc
Resolve npm security vulnerabilities via dependency overrides (#980)657f690
[bot] Update dist directory9d6bacd
Update @actions/cache and @actions/artifact,
stop ignoring them in Dependabot...79f6b19
[bot] Update dist directory6781648
Bump the npm-dependencies group in /sources with 5 updates (#977)a3b40d2
[bot] Update dist directorySourced from actions/stale's releases.
v11.0.0
What's Changed
Enhancement
- Migrate to ESM and update dependencies by
@chiranjib-swainin actions/stale#1350Dependency Update
- Override brace-expansion to 5.0.8 to address 24 high-severity dependency vulnerabilities by
@dependabotin actions/stale#1351Full Changelog: https://github.com/actions/stale/compare/v10...v11.0.0
v10.4.0
What's Changed
Bug Fix
- Fixed
only-issue-typesvalidation by@trueberrylessin actions/stale#1338Dependency Updates
- Bump undici to 6.27.0 via override, clean up stale license files, and version to 10.4.0. by
@dependabotin actions/stale#1342New Contributors
@trueberrylessmade their first contribution in actions/stale#1338Full Changelog: https://github.com/actions/stale/compare/v10.3.0...v10.4.0
v10.3.0
What's Changed
Bug Fix
- Enhancement: ignore stale labeling events by
@shamoonin actions/stale#1311Dependency Updates
- Upgrade dependencies (
@actions/core,@octokit/plugin-retry,@typescript-eslint) by@Copilotin actions/stale#1335New Contributors
@shamoonmade their first contribution in actions/stale#1311Full Changelog: https://github.com/actions/stale/compare/v10...v10.3.0
v10.2.0
What's Changed
Bug Fix
- Fix checking state cache (fix #1136) and switch to Octokit helper methods by
@itchynyin actions/stale#1152Dependency Updates
- Upgrade js-yaml from 4.1.0 to 4.1.1 by
@dependabotin actions/stale#1304- Upgrade lodash from 4.17.21 to 4.17.23 by
@dependabotin actions/stale#1313- Upgrade actions/cache from 4.0.3 to 5.0.2 and actions/github from 5.1.1 to 7.0.0 by
@chiranjib-swainin actions/stale#1312New Contributors
@itchynymade their first contribution in actions/stale#1152Full Changelog: https://github.com/actions/stale/compare/v10...v10.2.0
... (truncated)
Sourced from actions/stale's changelog.
Changelog
[10.1.0]
What's Changed
- Add only-issue-types option to filter issues by type by
@Bibo-Joshiin actions/stale#1255[10.0.0]
What's Changed
Breaking Changes
- Upgrade to node 24 by
@salmanmkcin actions/stale#1279 Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. Release NotesEnhancement
- Introducing sort-by option by
@suyashgaonkarin actions/stale#1254Dependency Upgrades
- Upgrade actions/publish-immutable-action from 0.0.3 to 0.0.4 by
@dependabot[bot] in actions/stale#1186- Upgrade undici from 5.28.4 to 5.28.5 by
@dependabot[bot] in actions/stale#1201- Upgrade
@action/cachefrom 4.0.0 to 4.0.2 by@aparnajyothi-yin actions/stale#1226- Upgrade
@action/cachefrom 4.0.2 to 4.0.3 by@suyashgaonkarin actions/stale#1233- Upgrade undici from 5.28.5 to 5.29.0 by
@dependabot[bot] in actions/stale#1251- Upgrade form-data to bring in fix for critical vulnerability by
@gowridurgadin actions/stale#1277Documentation changes
- Changelog update for recent releases by
@suyashgaonkarin actions/stale#1224- Permissions update in Readme by
@ghadimirin actions/stale#1248[9.1.0]
What's Changed
- Documentation update by
@Marukome0743in actions/stale#1116- Add workflow file for publishing releases to immutable action package by
@Jcambassin actions/stale#1179- Update undici from 5.28.2 to 5.28.4 by
@dependabotin actions/stale#1150- Update actions/checkout from 3 to 4 by
@dependabotin actions/stale#1091- Update actions/publish-action from 0.2.2 to 0.3.0 by
@dependabotin actions/stale#1147- Update ts-jest from 29.1.1 to 29.2.5 by
@dependabotin actions/stale#1175- Update
@actions/corefrom 1.10.1 to 1.11.1 by@dependabotin actions/stale#1191- Update
@types/jestfrom 29.5.11 to 29.5.14 by@dependabotin actions/stale#1193- Update
@actions/cachefrom 3.2.2 to 4.0.0 by@dependabotin actions/stale#1194[9.0.0]
Breaking Changes
- Action is now stateful: If the action ends because of operations-per-run then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). The state is reset when all the issues are processed. This should be considered for scheduling workflow runs.
- Version 9 of this action updated the runtime to Node.js 20. All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20.
... (truncated)
4391f3d
Fix 24 high severity vulnerabilities by overriding brace-expansion to
5.0.8 (...eaf9131
refactor: update imports to use ES module syntax and improve test
structure (...Sourced from github/codeql-action's releases.
v4.37.4
- This version of the CodeQL Action adds support for the
toolsinput for thecodeql-action/initstep to be specified using agithub-codeql-toolsrepository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value totoolcacheto always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided fortoolsin the workflow definition always takes precedence unless the value of the repository property starts with!. #4037- Update default CodeQL bundle version to 2.26.2. #4051
v4.37.3
No user facing changes.
v4.37.2
- The new address format for the
config-fileinput that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, theremote=prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023- The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007
v4.37.1
- Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
- Update default CodeQL bundle version to 2.26.1. #4019
v4.37.0
- Update default CodeQL bundle version to 2.26.0. #3995
- In addition to the existing input format, the
config-fileinput for thecodeql-action/initstep will soon support a new[owner/]repo[@ref][:path]format. All components except the repository name are optional. If omitted,ownerdefaults to the same owner as the repository the analysis is running for,reftomain, andpathto.github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973v4.36.3
No user facing changes.
v4.36.2
- Cache CodeQL CLI version information across Actions steps. #3943
- Reduce requests while waiting for analysis processing by using exponential backoff when polling SARIF processing status. #3937
- Update default CodeQL bundle version to 2.25.6. #3948
v4.36.1
No user facing changes.
v4.36.0
- Breaking change: Bump the minimum required CodeQL bundle version to 2.19.4. #3894
- Add support for SHA-256 Git object IDs. #3893
- Update default CodeQL bundle version to 2.25.5. #3926
v4.35.5
- We have improved how the JavaScript bundles for the CodeQL Action are generated to avoid duplication across bundles and reduce the size of the repository by around 70%. This should have no effect on the runtime behaviour of the CodeQL Action. #3899
- For performance and accuracy reasons, improved incremental analysis will now only be enabled on a pull request when diff-informed analysis is also enabled for that run. If diff-informed analysis is unavailable (for example, because the PR diff ranges could not be computed), the action will fall back to a full analysis. #3791
- If multiple inputs are provided for the GitHub-internal
analysis-kindsinput, onlycode-scanningwill be enabled. Theanalysis-kindsinput is experimental, for GitHub-internal use only, and may change without notice at any time. #3892- Added an experimental change which, when running a Code Scanning analysis for a PR with improved incremental analysis enabled, prefers CodeQL CLI versions that have a cached overlay-base database for the configured languages. This speeds up analysis for a repository when there is not yet a cached overlay-base database for the latest CLI version. We expect to roll this change out to everyone in May. #3880
v4.35.4
v4.35.3
- Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.19.3 and earlier. These versions of CodeQL were discontinued on 9 April 2026 alongside GitHub Enterprise Server 3.15, and will be unsupported by the next minor release of the CodeQL Action. #3837
- Configurations for private registries that use Cloudsmith or GCP OIDC are now accepted. #3850
- Best-effort connection tests for private registries now use
GETrequests instead ofHEADfor better compatibility with various registry implementations. For NuGet feeds, the test is now always performed against the service index. #3853- Fixed a bug where two diagnostics produced within the same millisecond could overwrite each other on disk, causing one of them to be lost. #3852
- Update default CodeQL bundle version to 2.25.3. #3865
... (truncated)
Sourced from github/codeql-action's changelog.
4.37.4 - 29 Jul 2026
- This version of the CodeQL Action adds support for the
toolsinput for thecodeql-action/initstep to be specified using agithub-codeql-toolsrepository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value totoolcacheto always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided fortoolsin the workflow definition always takes precedence unless the value of the repository property starts with!. #4037- Update default CodeQL bundle version to 2.26.2. #4051
4.37.3 - 22 Jul 2026
No user facing changes.
4.37.2 - 21 Jul 2026
- The new address format for the
config-fileinput that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, theremote=prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023- The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007
4.37.1 - 16 Jul 2026
- Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
- Update default CodeQL bundle version to 2.26.1. #4019
4.37.0 - 08 Jul 2026
- Update default CodeQL bundle version to 2.26.0. #3995
- In addition to the existing input format, the
config-fileinput for thecodeql-action/initstep will soon support a new[owner/]repo[@ref][:path]format. All components except the repository name are optional. If omitted,ownerdefaults to the same owner as the repository the analysis is running for,reftomain, andpathto.github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #39734.36.3 - 01 Jul 2026
No user facing changes.
18420e3
Merge pull request #4043
from github/mbg/ts/changelog7e8d897
Merge pull request #4046
from github/mbg/repo-prop/code-quality2d4c474
Log !analysisKindSupported case98c05a1
Fix argument validation in rollback-changelog.ts8289a49
Ignore repository property for unsupported analysis kinds2a8731c
Move config-file computation after determining the
analysisKinds3434fbb
Merge pull request #4044
from github/mbg/ff/promote-toolcache3013ac0
Promote AllowToolcacheInput feature74b15aa
Install JS deps if needed in post-release-mergeback
workflowf00f809
Fix checking keys rather than values