[GITHUB-ACTIONS] bump the github-actions group across 1 directory with 12 updates
Type: Pull Request
State: Closed
Association: Unknown
Comments: 1
(about 2 months ago)
(about 2 months ago)
(about 2 months ago)
dependencies github_actions
Bumps the github-actions group with 12 updates in the / directory:
| Package | From | To |
|---|---|---|
| actions/checkout | 6.0.1 |
6.0.2 |
| actions/setup-python | 6.1.0 |
6.2.0 |
| slackapi/slack-github-action | 2.1.1 |
3.0.1 |
| actions/create-github-app-token | 2.2.1 |
3.0.0 |
| actions/download-artifact | 7.0.0 |
8.0.1 |
| actions/upload-artifact | 6.0.0 |
7.0.0 |
| actions/stale | 10.1.1 |
10.2.0 |
| github/codeql-action | 4.31.9 |
4.35.1 |
| actions/dependency-review-action | 4.8.2 |
4.9.0 |
| hashicorp/setup-terraform | 3.1.2 |
4.0.0 |
| terraform-linters/setup-tflint | 6.2.1 |
6.2.2 |
| bridgecrewio/checkov-action | 12.3077.0 |
12.3092.0 |
Updates actions/checkout from 6.0.1 to 6.0.2
Release notes
Sourced from actions/checkout's releases.
v6.0.2
What's Changed
- Add orchestration_id to git user-agent when ACTIONS_ORCHESTRATION_ID is set by
@TingluoHuangin actions/checkout#2355- Fix tag handling: preserve annotations and explicit fetch-tags by
@ericsciplein actions/checkout#2356Full Changelog: https://github.com/actions/checkout/compare/v6.0.1...v6.0.2
Changelog
Sourced from actions/checkout's changelog.
Changelog
v6.0.2
- Fix tag handling: preserve annotations and explicit fetch-tags by
@ericsciplein actions/checkout#2356v6.0.1
- Add worktree support for persist-credentials includeIf by
@ericsciplein actions/checkout#2327v6.0.0
- Persist creds to a separate file by
@ericsciplein actions/checkout#2286- Update README to include Node.js 24 support details and requirements by
@salmanmkcin actions/checkout#2248v5.0.1
- Port v6 cleanup to v5 by
@ericsciplein actions/checkout#2301v5.0.0
- Update actions checkout to use node 24 by
@salmanmkcin actions/checkout#2226v4.3.1
- Port v6 cleanup to v4 by
@ericsciplein actions/checkout#2305v4.3.0
- docs: update README.md by
@motssin actions/checkout#1971- Add internal repos for checking out multiple repositories by
@mouismailin actions/checkout#1977- Documentation update - add recommended permissions to Readme by
@benwellsin actions/checkout#2043- Adjust positioning of user email note and permissions heading by
@joshmgrossin actions/checkout#2044- Update README.md by
@nebuk89in actions/checkout#2194- Update CODEOWNERS for actions by
@TingluoHuangin actions/checkout#2224- Update package dependencies by
@salmanmkcin actions/checkout#2236v4.2.2
url-helper.tsnow leverages well-known environment variables by@jww3in actions/checkout#1941- Expand unit test coverage for
isGhesby@jww3in actions/checkout#1946v4.2.1
- Check out other refs/* by commit if provided, fall back to ref by
@orhantoyin actions/checkout#1924v4.2.0
- Add Ref and Commit outputs by
@lucacomein actions/checkout#1180- Dependency updates by
@dependabot- actions/checkout#1777, actions/checkout#1872v4.1.7
- Bump the minor-npm-dependencies group across 1 directory with 4 updates by
@dependabotin actions/checkout#1739- Bump actions/checkout from 3 to 4 by
@dependabotin actions/checkout#1697- Check out other refs/* by commit by
@orhantoyin actions/checkout#1774- Pin actions/checkout's own workflows to a known, good, stable version. by
@jww3in actions/checkout#1776v4.1.6
- Check platform to set archive extension appropriately by
@cory-millerin actions/checkout#1732
... (truncated)
Commits
de0fac2Fix tag handling: preserve annotations and explicit fetch-tags (#2356)064fe7fAdd orchestration_id to git user-agent when ACTIONS_ORCHESTRATION_ID is set (...- See full diff in compare view
Updates actions/setup-python from 6.1.0 to 6.2.0
Release notes
Sourced from actions/setup-python's releases.
v6.2.0
What's Changed
Dependency Upgrades
- Upgrade dependencies to Node 24 compatible versions by
@salmanmkcin actions/setup-python#1259- Upgrade urllib3 from 2.5.0 to 2.6.3 in
/__tests__/databy@dependabotin actions/setup-python#1253 and actions/setup-python#1264Full Changelog: https://github.com/actions/setup-python/compare/v6...v6.2.0
Commits
Updates slackapi/slack-github-action from 2.1.1 to 3.0.1
Release notes
Sourced from slackapi/slack-github-action's releases.
Slack GitHub Action v3.0.1
What's Changed
Alongside the breaking changes of
@v3.0.0and a new technique to run Slack CLI commands, we tried the wrong name to publish to the GitHub Marketplace 🐙 This action is now noted as The Slack GitHub Action in listings 🎶 ✨:art: Maintenance
- chore: use a unique title for marketplace in slackapi/slack-github-action#576 - Thanks
@zimeg!- chore(release): tag version 3.0.1 in slackapi/slack-github-action#577 - Thanks
@zimeg!Full Changelog: https://github.com/slackapi/slack-github-action/compare/v3.0.0...v3.0.1
Slack GitHub Action v3.0.0
The
@v3.0.0release had a hiccup on publish and we recommend using@v3.0.1or a more recent version when updating! Oops!🎽 Running Slack CLI commands and the active Node runtime, both included in this release 👟 ✨
⚠️ Breaking change: Node.js 24 the runtime
This major version updates the GitHub Actions required runtime to Node.js 24. Most GitHub-hosted runners already include this, but self-hosted runners may need to be updated ahead of planned deprecations of Node 20 on GitHub Actions runners.
📺 Enhancement: Run Slack CLI commands
This release introduces a new technique for running Slack CLI commands directly in GitHub Actions workflows. Use this to install the latest version (or a specific one) of the CLI and execute commands like
deployfor merges to main,manifest validatewith tests, and other commands.Gather a token using the following CLI command to store with repo secrets, then get started with an example below:
$ slack auth token🧪 Validate an app manifest on pull requests
Check that your app manifest is valid before merging changes:
- name: Validate the manifest uses: slackapi/slack-github-action/cli@v3.0.0 with: command: "manifest validate --app ${{ vars.SLACK_APP_ID }}" token: ${{ secrets.SLACK_SERVICE_TOKEN }}🚀 Deploy your app on push to main
Automate deployments whenever changes land on your main branch:
... (truncated)
Commits
af78098Releaseadd1a00chore(release): tag version 3.0.1 (#577)2bc9e7achore: use a unique title for marketplace (#576)c5d43dachore(release): tag version 3.0.0 (#575)963b979build(deps): bump@slack/web-apifrom 7.14.1 to 7.15.0 (#574)90b7328build(deps): bump@slack/loggerfrom 4.0.0 to 4.0.1 (#573)e45cb89feat: support slack cli commands with composite action inputs (#560)0aed2c2build(deps): bump https-proxy-agent from 7.0.6 to 8.0.0 (#572)4795f96build(deps-dev): bump sinon from 21.0.1 to 21.0.2 (#571)bd9e2cebuild(deps): bump actions/setup-node from 6.2.0 to 6.3.0 (#569)- Additional commits viewable in compare view
Updates actions/create-github-app-token from 2.2.1 to 3.0.0
Release notes
Sourced from actions/create-github-app-token's releases.
v3.0.0
3.0.0 (2026-03-14)
- feat!: node 24 support (#275) (2e564a0)
- fix!: require
NODE_USE_ENV_PROXYfor proxy support (#342) (4451bcb)Bug Fixes
BREAKING CHANGES
- Custom proxy handling has been removed. If you use HTTP_PROXY or HTTPS_PROXY, you must now also set NODE_USE_ENV_PROXY=1 on the action step.
- Requires Actions Runner v2.327.1 or later if you are using a self-hosted runner.
v3.0.0-beta.6
3.0.0-beta.6 (2026-03-13)
Bug Fixes
- deps: bump
@actions/corefrom 1.11.1 to 3.0.0 (#337) (b044133)- deps: bump minimatch from 9.0.5 to 9.0.9 (#335) (5cbc656)
- deps: bump the production-dependencies group with 4 updates (#336) (6bda5bc)
- deps: bump undici from 7.16.0 to 7.18.2 (#323) (b4f638f)
v3.0.0-beta.5
3.0.0-beta.5 (2026-03-13)
BREAKING CHANGES
- Custom proxy handling has been removed. If you use HTTP_PROXY or HTTPS_PROXY, you must now also set NODE_USE_ENV_PROXY=1 on the action step.
v3.0.0-beta.4
3.0.0-beta.4 (2026-03-13)
Bug Fixes
... (truncated)
Commits
f8d387bbuild(release): 3.0.0 [skip ci]d2129bdstyle: remove extra blank line in release workflow77b94efbuild: refresh generated artifacts3ab4c66chore: move undici to devDependencies739cf66docs: update README action versionsdb40289build(deps): bump actions versions in test.yml496a7actest: migrate from AVA to Node.js native test runner (#346)3870dc3Rename end-to-end proxy job in test workflow4451bcbfix!: requireNODE_USE_ENV_PROXYfor proxy support (#342)dce0ab0fix: remove custom proxy handling (#143)- Additional commits viewable in compare view
Updates actions/download-artifact from 7.0.0 to 8.0.1
Release notes
Sourced from actions/download-artifact's releases.
v8.0.1
What's Changed
- Support for CJK characters in the artifact name by
@danwkennedyin actions/download-artifact#471- Add a regression test for artifact name + content-type mismatches by
@danwkennedyin actions/download-artifact#472Full Changelog: https://github.com/actions/download-artifact/compare/v8...v8.0.1
v8.0.0
v8 - What's new
[!IMPORTANT] actions/download-artifact@v8 has been migrated to an ESM module. This should be transparent to the caller but forks might need to make significant changes.
[!IMPORTANT] Hash mismatches will now error by default. Users can override this behavior with a setting change (see below).
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 totrue.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
Commits
3e5f45bAdd regression tests for CJK characters (#471)e6d03f6Add a regression test for artifact name + content-type mismatches (#472)70fc10cMerge pull request #461 from actions/danwkennedy/digest-mismatch-behaviorf258da9Add change docsccc058eFix linting issuesbd7976bAdd a setting to specify what to do on hash mismatch and default it toerrorac21fcfMerge pull request #460 from actions/danwkennedy/download-no-unzip15999bfAdd note about package bumps974686eBump the version tov8and add release notesfbe48b1Update test names to make it clearer what they do- Additional commits viewable in compare view
Updates actions/upload-artifact from 6.0.0 to 7.0.0
Release notes
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
Commits
Updates actions/stale from 10.1.1 to 10.2.0
Release notes
Sourced from actions/stale's releases.
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
Commits
b5d41d4build(deps-dev): bump lodash from 4.17.21 to 4.17.23 (#1313)dcd2b94Fix punycode and url.parse Deprecation Warnings (#1312)d6f8a33build(deps-dev): bump js-yaml from 4.1.0 to 4.1.1 (#1304)a21a081Fix checking state cache (fix #1136), also switch to octokit methods (#1152)- See full diff in compare view
Updates github/codeql-action from 4.31.9 to 4.35.1
Release notes
Sourced from github/codeql-action's releases.
v4.35.1
- Fix incorrect minimum required Git version for improved incremental analysis: it should have been 2.36.0, not 2.11.0. #3781
v4.35.0
- Reduced the minimum Git version required for improved incremental analysis from 2.38.0 to 2.11.0. #3767
- Update default CodeQL bundle version to 2.25.1. #3773
v4.34.1
- Downgrade default CodeQL bundle version to 2.24.3 due to issues with a small percentage of Actions and JavaScript analyses. #3762
v4.34.0
- Added an experimental change which disables TRAP caching when improved incremental analysis is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. #3569
- We are rolling out improved incremental analysis to C/C++ analyses that use build mode
none. We expect this rollout to be complete by the end of April 2026. #3584- Update default CodeQL bundle version to 2.25.0. #3585
v4.33.0
Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #3562
To opt out of this change:
- Repositories owned by an organization: Create a custom repository property with the name
github-codeql-file-coverage-on-prsand the type "True/false", then set this property totruein the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set theCODEQL_ACTION_FILE_COVERAGE_ON_PRSenvironment variable totruein your workflow.- User-owned repositories using default setup: Switch to an advanced setup workflow and set the
CODEQL_ACTION_FILE_COVERAGE_ON_PRSenvironment variable totruein your workflow.- User-owned repositories using advanced setup: Set the
CODEQL_ACTION_FILE_COVERAGE_ON_PRSenvironment variable totruein your workflow.Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #3557
The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as
github-codeql-disable-overlaythat was previously only available on GitHub.com. #3559Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #3563
Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #3564
A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. #3570
v4.32.6
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
v4.32.4
- 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
v4.32.3
- 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
... (truncated)
Changelog
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]
- The Git version 2.36.0 requirement for improved incremental analysis now only applies to repositories that contain submodules. #3789
- Python analysis on GHES no longer extracts the standard library, relying instead on models of the standard library. This should result in significantly faster extraction and analysis times, while the effect on alerts should be minimal. #3794
4.35.1 - 27 Mar 2026
- Fix incorrect minimum required Git version for improved incremental analysis: it should have been 2.36.0, not 2.11.0. #3781
4.35.0 - 27 Mar 2026
- Reduced the minimum Git version required for improved incremental analysis from 2.38.0 to 2.11.0. #3767
- Update default CodeQL bundle version to 2.25.1. #3773
4.34.1 - 20 Mar 2026
- Downgrade default CodeQL bundle version to 2.24.3 due to issues with a small percentage of Actions and JavaScript analyses. #3762
4.34.0 - 20 Mar 2026
- Added an experimental change which disables TRAP caching when improved incremental analysis is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. #3569
- We are rolling out improved incremental analysis to C/C++ analyses that use build mode
none. We expect this rollout to be complete by the end of April 2026. #3584- Update default CodeQL bundle version to 2.25.0. #3585
4.33.0 - 16 Mar 2026
Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #3562
To opt out of this change:
- Repositories owned by an organization: Create a custom repository property with the name
github-codeql-file-coverage-on-prsand the type "True/false", then set this property totruein the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set theCODEQL_ACTION_FILE_COVERAGE_ON_PRSenvironment variable totruein your workflow.- User-owned repositories using default setup: Switch to an advanced setup workflow and set the
CODEQL_ACTION_FILE_COVERAGE_ON_PRSenvironment variable totruein your workflow.- User-owned repositories using advanced setup: Set the
CODEQL_ACTION_FILE_COVERAGE_ON_PRSenvironment variable totruein your workflow.Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #3557
The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as
github-codeql-disable-overlaythat was previously only available on GitHub.com. #3559Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #3563
Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #3564
A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. #3570
4.32.6 - 05 Mar 2026
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
... (truncated)
Commits
c10b806Merge pull request #3782 from github/update-v4.35.1-d6d1743b8c5ffd06Update changelog for v4.35.1d6d1743Merge pull request #3781 from github/henrymercer/update-git-minimum-version65d2efaAdd changelog note2437b20Update minimum git version for overlay to 2.36.0ea5f719Merge pull request #3775 from github/dependabot/npm_and_yarn/node-forge-1.4.045ceeeaMerge pull request #3777 from github/mergeback/v4.35.0-to-main-b8bb9f2824448c9Rebuild7c51060Update changelog and version after v4.35.0b8bb9f2Merge pull request #3776 from github/update-v4.35.0-0078ad667- Additional commits viewable in compare view
Updates actions/dependency-review-action from 4.8.2 to 4.9.0
Release notes
Sourced from actions/dependency-review-action's releases.
Dependency Review Action 4.9.0
This feature release contains a couple of notable changes:
- There is a new configuration option
show_patched_versionswhich will add a column to the output, showing the fix version of each vulnerable dependency. Thanks@felickz!- Runs which do not display OpenSSF scorecards no longer fetch scorecard information; previously it was fetched regardless of whether or not it was displayed, causing unneccessary slowness. Great catch
@jantiebot!- There are a couple of fixes to purl parsing which should improve match accuracy for
allow-package-dependencylists, including case (in)sensitivity and url-encoded namespaces Thanks@juxtin!What's Changed
- Compare normalized purls to account for encoding quirks by
@juxtinin actions/dependency-review-action#1056- Make purl comparisons case insensitive by
@juxtinin actions/dependency-review-action#1057- Feat: Add
Patched VersiontoVulnerabilitiessummary by@felickzin actions/dependency-review-action#1045- fix: only get scorecard levels if user wants to see the OpenSSF scorecard by
@jantiebotin actions/dependency-review-action#1060- Bump actions/stale from 10.1.0 to 10.2.0 by
@dependabot[bot] in actions/dependency-review-action#1058- Bump actions/checkout from 4 to 6 by
@dependabot[bot] in actions/dependency-review-action#1021- Updates for release 4.9.0 by
@ahpookin actions/dependency-review-action#1064New Contributors
@jantiebotmade their first contribution in actions/dependency-review-action#1060Full Changelog: https://github.com/actions/dependency-review-action/compare/v4.8.3...v4.9.0
4.8.3
Dependency Review Action v4.8.3
This is a bugfix release that updates a number of upstream dependencies and includes a fix for the earlier feature that detected oversized summaries and upload them as artifacts, which could occasionally crash the action.
We have also updated the release process to use a long-lived
v4branch for the action, instead of a force-pushed tag, which aligns better with git branching strategies; the change should be transparent to end users.What's Changed
- GitHub Actions can't push to our protected main by
@dangoorin actions/dependency-review-action#1017- Bump actions/stale from 9.1.0 to 10.1.0 by
@dependabot[bot] in actions/dependency-review-action#995- Bump github/codeql-action from 3 to 4 by
@dependabot[bot] in actions/dependency-review-action#1003- Bump actions/setup-node from 4 to 6 by
@dependabot[bot] inPackage Dependencies
Package:
actions/upload-artifactEcosystem:
actionsVersion Change:
6.0.0 → 7.0.0Update Type:
MajorPackage:
actions/download-artifactEcosystem:
actionsVersion Change:
7.0.0 → 8.0.1Update Type:
MajorPackage:
actions/dependency-review-actionEcosystem:
actionsVersion Change:
4.8.2 → 4.9.0Update Type:
MinorPackage:
bridgecrewio/checkov-actionEcosystem:
actionsVersion Change:
12.3077.0 → 12.3092.0Update Type:
MinorPackage:
slackapi/slack-github-actionEcosystem:
actionsVersion Change:
2.1.1 → 3.0.1Update Type:
MajorPackage:
actions/create-github-app-tokenEcosystem:
actionsVersion Change:
2.2.1 → 3.0.0Update Type:
MajorPackage:
hashicorp/setup-terraformEcosystem:
actionsVersion Change:
3.1.2 → 4.0.0Update Type:
MajorPackage:
terraform-linters/setup-tflintEcosystem:
actionsVersion Change:
6.2.1 → 6.2.2Update Type:
Patch
Technical Details
| ID: | 15228710 |
| UUID: | 4206080081 |
| Node ID: | PR_kwDOOZgZRc7QADt4 |
| Host: | GitHub |
| Repository: | tagdots-dev/python-test |