chore(deps): bump actions/checkout from 6 to 6.0.3 in the actions group across 1 directory#810
Conversation
|
Why did Dependabot go from v6 to v6.0.3? It's not supposed to do that, it's supposed to keep the same style. And there's a v7 now too. |
|
@dependabot recreate |
Bumps the actions group with 1 update in the / directory: [actions/checkout](https://github.com/actions/checkout). Updates `actions/checkout` from 6 to 6.0.3 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v6...v6.0.3) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 6.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
91d0399 to
3ae1d4f
Compare
|
And Dependabot wiped the "Dependabot commands and options" section on recreation. And didn't fix the problem. |
|
Ahh, I know why (not the commands wipe, but the v6 -> v6.0.3 and ignoring of v7): Lines 8 to 9 in 40b0e22 That basically forces an old tag if the moving tag is less than 7 days old. |
|
The main change in v7 is extra security (protection against "pwn request" vulnerabilities), ironically. |
|
This is not tied to the guide / cookie (separate updates), so maybe we should just go full frozen, and only have floating tags for the guide / cookie. |
so, close this, and 7 days from now it will open a new one bumping to v7? |
|
I think so. But since this is our internal actions, we can go ahead and make this properly fixed and hashed, with a lower frequency, and only keep the public ones loose (since they show up in a guide, and should be simple and easy to get started with). |
Bumps the actions group with 1 update in the / directory: actions/checkout.
Updates
actions/checkoutfrom 6 to 6.0.3Release notes
Sourced from actions/checkout's releases.
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
Commits