Sourced from actions/upload-artifact's releases.
v7.0.0
v7 What's new
Direct Uploads
Adds support for uploading single files directly (unzipped). Callers can set the new
archiveparameter tofalseto skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. Thenameparameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.ESM
To support new versions of the
@actions/*packages, we've upgraded the package to ESM.What's Changed
- Add proxy integration test by
@Link- in actions/upload-artifact#754- Upgrade the module to ESM and bump dependencies by
@danwkennedyin actions/upload-artifact#762- Support direct file uploads by
@danwkennedyin actions/upload-artifact#764New Contributors
@Link- made their first contribution in actions/upload-artifact#754Full Changelog: https://github.com/actions/upload-artifact/compare/v6...v7.0.0
Sourced from actions/download-artifact's releases.
v8.0.0
v8 - What's new
Direct downloads
To support direct uploads in
actions/upload-artifact, the action will no longer attempt to unzip all downloaded files. Instead, the action checks theContent-Typeheader ahead of unzipping and skips non-zipped files. Callers wishing to download a zipped file as-is can also set the newskip-decompressparameter tofalse.Enforced checks (breaking)
A previous release introduced digest checks on the download. If a download hash didn't match the expected hash from the server, the action would log a warning. Callers can now configure the behavior on mismatch with the
digest-mismatchparameter. To be secure by default, we are now defaulting the behavior toerrorwhich will fail the workflow run.ESM
To support new versions of the @actions/* packages, we've upgraded the package to ESM.
What's Changed
- Don't attempt to un-zip non-zipped downloads by
@danwkennedyin actions/download-artifact#460- Add a setting to specify what to do on hash mismatch and default it to
errorby@danwkennedyin actions/download-artifact#461Full Changelog: https://github.com/actions/download-artifact/compare/v7...v8.0.0
70fc10c
Merge pull request #461
from actions/danwkennedy/digest-mismatch-behaviorf258da9
Add change docsccc058e
Fix linting issuesbd7976b
Add a setting to specify what to do on hash mismatch and default it to
errorac21fcf
Merge pull request #460
from actions/danwkennedy/download-no-unzip15999bf
Add note about package bumps974686e
Bump the version to v8 and add release notesfbe48b1
Update test names to make it clearer what they do96bf374
One more test fixb8c4819
Fix skip decompress testSourced from github/codeql-action's releases.
v4.32.5
- Repositories owned by an organization can now set up the
github-codeql-disable-overlaycustom repository property to disable improved incremental analysis for CodeQL. First, create a custom repository property with the namegithub-codeql-disable-overlayand the type "True/false" in the organization's settings. Then in the repository's settings, set this property totrueto disable improved incremental analysis. For more information, see Managing custom properties for repositories in your organization. This feature is not yet available on GitHub Enterprise Server. #3507- Added an experimental change so that when improved incremental analysis fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. #3487
- The minimum memory check for improved incremental analysis is now skipped for CodeQL 2.24.3 and later, which has reduced peak RAM usage. #3515
- Reduced log levels for best-effort private package registry connection check failures to reduce noise from workflow annotations. #3516
- Added an experimental change which lowers the minimum disk space requirement for improved incremental analysis, enabling it to run on standard GitHub Actions runners. We expect to roll this change out to everyone in March. #3498
- Added an experimental change which allows the
start-proxyaction to resolve the CodeQL CLI version from feature flags instead of using the linked CLI bundle version. We expect to roll this change out to everyone in March. #3512- The previously experimental changes from versions 4.32.3, 4.32.4, 3.32.3 and 3.32.4 are now enabled by default. #3503, #3504
Sourced from github/codeql-action's changelog.
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
[UNRELEASED]
No user facing changes.
4.32.5 - 02 Mar 2026
- Repositories owned by an organization can now set up the
github-codeql-disable-overlaycustom repository property to disable improved incremental analysis for CodeQL. First, create a custom repository property with the namegithub-codeql-disable-overlayand the type "True/false" in the organization's settings. Then in the repository's settings, set this property totrueto disable improved incremental analysis. For more information, see Managing custom properties for repositories in your organization. This feature is not yet available on GitHub Enterprise Server. #3507- Added an experimental change so that when improved incremental analysis fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. #3487
- The minimum memory check for improved incremental analysis is now skipped for CodeQL 2.24.3 and later, which has reduced peak RAM usage. #3515
- Reduced log levels for best-effort private package registry connection check failures to reduce noise from workflow annotations. #3516
- Added an experimental change which lowers the minimum disk space requirement for improved incremental analysis, enabling it to run on standard GitHub Actions runners. We expect to roll this change out to everyone in March. #3498
- Added an experimental change which allows the
start-proxyaction to resolve the CodeQL CLI version from feature flags instead of using the linked CLI bundle version. We expect to roll this change out to everyone in March. #3512- The previously experimental changes from versions 4.32.3, 4.32.4, 3.32.3 and 3.32.4 are now enabled by default. #3503, #3504
4.32.4 - 20 Feb 2026
- Update default CodeQL bundle version to 2.24.2. #3493
- Added an experimental change which improves how certificates are generated for the authentication proxy that is used by the CodeQL Action in Default Setup when private package registries are configured. This is expected to generate more widely compatible certificates and should have no impact on analyses which are working correctly already. We expect to roll this change out to everyone in February. #3473
- When the CodeQL Action is run with debugging enabled in Default Setup and private package registries are configured, the "Setup proxy for registries" step will output additional diagnostic information that can be used for troubleshooting. #3486
- Added a setting which allows the CodeQL Action to enable network debugging for Java programs. This will help GitHub staff support customers with troubleshooting issues in GitHub-managed CodeQL workflows, such as Default Setup. This setting can only be enabled by GitHub staff. #3485
- Added a setting which enables GitHub-managed workflows, such as Default Setup, to use a nightly CodeQL CLI release instead of the latest, stable release that is used by default. This will help GitHub staff support customers whose analyses for a given repository or organization require early access to a change in an upcoming CodeQL CLI release. This setting can only be enabled by GitHub staff. #3484
4.32.3 - 13 Feb 2026
- Added experimental support for testing connections to private package registries. This feature is not currently enabled for any analysis. In the future, it may be enabled by default for Default Setup. #3466
4.32.2 - 05 Feb 2026
4.32.1 - 02 Feb 2026
- A warning is now shown in Default Setup workflow logs if a private package registry is configured using a GitHub Personal Access Token (PAT), but no username is configured. #3422
- Fixed a bug which caused the CodeQL Action to fail when repository properties cannot successfully be retrieved. #3421
4.32.0 - 26 Jan 2026
4.31.11 - 23 Jan 2026
- When running a Default Setup workflow with Actions debugging enabled, the CodeQL Action will now use more unique names when uploading logs from the Dependabot authentication proxy as workflow artifacts. This ensures that the artifact names do not clash between multiple jobs in a build matrix. #3409
- Improved error handling throughout the CodeQL Action. #3415
- Added experimental support for automatically excluding generated files from the analysis. This feature is not currently enabled for any analysis. In the future, it may be enabled by default for some GitHub-managed analyses. #3318
- The changelog extracts that are included with releases of the CodeQL Action are now shorter to avoid duplicated information from appearing in Dependabot PRs. #3403
... (truncated)
c793b71
Merge pull request #3523
from github/update-v4.32.5-ca42bf22606cd615
Soften language re overlay failuresf5516c6
Improve changelog97519e1
Update release date05259a1
Add more changelog notes01ee2f7
Add changelog notesc72d9a4
Update changelog for v4.32.5ca42bf2
Merge pull request #3522
from github/henrymercer/update-supported-versions-table6704d80
Merge pull request #3520
from github/dependabot/npm_and_yarn/fast-xml-parser-...76348c0
Merge pull request #3521
from github/dependabot/npm_and_yarn/minimatch-3.1.5