Skip to content

Build(deps): Bump actions/checkout from 4 to 7 - #18

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/checkout-7
Open

Build(deps): Bump actions/checkout from 4 to 7#18
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/checkout-7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 26, 2026

Copy link
Copy Markdown
Contributor

Bumps actions/checkout from 4 to 7.

Release notes

Sourced from actions/checkout's releases.

v7.0.0

What's Changed

New Contributors

Full Changelog: actions/checkout@v6.0.3...v7.0.0

v6.1.0

What's Changed

https://github.blog/changelog/2026-06-18-safer-pull_request_target-defaults-for-github-actions-checkout/ for more details about this breaking change

Full Changelog: actions/checkout@v6.0.3...v6.1.0

v6.0.3

What's Changed

New Contributors

Full Changelog: actions/checkout@v6...v6.0.3

v6.0.2

What's Changed

Full Changelog: actions/checkout@v6.0.1...v6.0.2

v6.0.1

What's Changed

... (truncated)

Changelog

Sourced from actions/checkout's changelog.

Changelog

v7.0.1

v7.0.0

v6.0.3

v6.0.2

v6.0.1

v6.0.0

v5.0.1

v5.0.0

v4.3.1

v4.3.0

v4.2.2

v4.2.1

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 7.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v4...v7)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jul 26, 2026
@codecov

codecov Bot commented Jul 26, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@rowan-claude

Copy link
Copy Markdown
Contributor

The bump itself is fine, and the "4 → 7" jump is smaller than it looks: on main, actions/checkout@v7 is already at seven call sites and v4 survived only at ci.yml:152, the STANDARD.md matches upstream job — added with v4 hardcoded while the rest of the file had moved. This is the last straggler coming into line on a version this repo's CI already runs. (Same straggler, same cause, as serialize.go#12 earlier today.)

I checked the one v7.0.0 behavior change that could actually bite — it refuses to check out fork PRs under pull_request_target / workflow_run. ci.yml uses neither event, and cla.yml does use pull_request_target but never checks anything out. No exposure.

The red check is not this PR. VersionFull matches upstream is failing identically on main (bb28672), so it arrived before the bump and the bump cannot have caused it — nothing in a checkout version reaches that job.

Its cause, verified against the source rather than inferred: upstream cut v1.4.2 at 2026-07-26T00:00:28Z and netcode.h now says NETCODE_VERSION_FULL "1.4.2", while netcode.go:45 still says 1.4.0. The drift check is doing exactly the job it was written for.

What the two intervening releases imply here, as far as I can see from the release notes and this tree:

  • 1.4.1 is spec-only — netcode.c/netcode.h byte-identical to 1.4.0, the change being STANDARD.md scoping the nonce guarantee to a server run plus optional restart mitigations. This repo's vendored STANDARD.md already matches upstream (that check is green), and the restart nonce fix is ported and pinned here already — restart_test.go, and the retract block in go.mod.
  • 1.4.2 is the vendored libsodium 1.0.21/1.0.22 hardenings in the C tree's sodium/ subset. This port has no vendored crypto — it's golang.org/x/crypto — so there is no direct analogue to carry across.

So this looks like a version-constant bump (VersionFull and VersionPatch at netcode.go:45,48) rather than a port of behavior — but the job's own instructions say read what changed and port whatever it implies, and that read is the maintainer's, not mine. Flagging it rather than making it, since it's a separate change from this PR.

Not merging: netcode.go is one of the flagship ports, so it goes to Glenn even when the diff is one line and the rest of CI is green.

— Rowan (AI collaborator, mas-bandwidth)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant