Skip to content

Bump actions/checkout from 4.4.0 to 7.0.1 - #1460

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

Bump actions/checkout from 4.4.0 to 7.0.1#1460
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/checkout-7.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 13, 2026

Copy link
Copy Markdown

Bumps actions/checkout from 4.4.0 to 7.0.1.

Release notes

Sourced from actions/checkout's releases.

v7.0.1

What's Changed

Full Changelog: actions/checkout@v7...v7.0.1

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

... (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.4.0 to 7.0.1.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@11d5960...3d3c42e)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: 7.0.1
  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 Aug 13, 2026
@ymichael ymichael closed this Aug 13, 2026
@dependabot @github

dependabot Bot commented on behalf of github Aug 13, 2026

Copy link
Copy Markdown
Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/github_actions/actions/checkout-7.0.1 branch August 13, 2026 04:39
ymichael added a commit that referenced this pull request Aug 13, 2026
## Summary

- upgrade all pinned GitHub Actions consistently across workflows and
the local composite action
- combine the two GitHub Actions update locations into one
`directories:` entry
- add a wildcard Dependabot group so future action upgrades arrive in
one PR

This replaces #1460, #1461, #1462, #1463, #1464, #1465, #1466, and
#1467.

## SHA verification

All target tags were independently resolved against their upstream
repositories:

| Action | Tag | Verified commit |
| --- | --- | --- |
| `actions/checkout` | `v7.0.1` |
`3d3c42e5aac5ba805825da76410c181273ba90b1` |
| `pnpm/action-setup` | `v6.0.10` |
`0977fd99725f1db4007ccb2928dbb4e90d06cc86` |
| `actions/upload-artifact` | `v7.0.1` |
`043fb46d1a93c77aae656e7c1c64a875d1fc6a0a` |
| `actions/setup-node` | `v7.0.0` |
`820762786026740c76f36085b0efc47a31fe5020` |
| `actions/cache` | `v6.1.0` |
`55cc8345863c7cc4c66a329aec7e433d2d1c52a9` |

## Breaking-change review

- **`actions/setup-node` 4 → 7: safe.** v5 moved the action runtime to
Node 24 and enabled automatic package-manager caching; v6 limited
automatic caching to npm and removed `always-auth`; v7 removed the dummy
`NODE_AUTH_TOKEN`. The cache consumers explicitly request `cache: pnpm`.
The npm publish job intentionally has no `NODE_AUTH_TOKEN`, grants
`id-token: write`, runs on a GitHub-hosted runner with Node 24, and
upgrades npm to at least 11.5.1, so removing the dummy value preserves
the trusted-publishing OIDC path. `publish-bb-app.yml` was not
dispatched because its scheduled path performs a real publication.
- **`actions/checkout` 4 → 7: safe.** v5's Node 24 runtime requirement
is satisfied by the GitHub-hosted runners. v6 moved persisted
credentials out of the repository into runner temp, but
`persist-credentials` remains enabled and the workflows do not inspect
the old storage location. The defaults used here—no submodules and
shallow fetch—remain compatible. v7's fork-PR guard does not affect
these workflow triggers.
- **`actions/cache` 4 → 6: safe.** The starting v4.3.0 already used the
cache service v2 migration. v5 moved to Node 24; v6 moved action
internals to ESM; v6.1 improves read-only cache handling. Both call
sites use explicit keys and ordered restore prefixes, with no dependency
on changed internals.
- **`pnpm/action-setup` 4 → 6: safe.** v5 moved the action runtime to
Node 24 and v6 added pnpm 11 support. Every call site explicitly
requests pnpm 9.15.0, matching the root `packageManager`, and keeps
`run_install: false`, so version inference and install behavior do not
change.
- **`actions/upload-artifact` 4 → 7: safe.** Both consumers already
start on v4.6.2, after v4's immutable artifact and hidden-file changes.
Each job performs one upload with its own artifact name, so it does not
rely on implicit same-name merging. v5/v6's Node 24 requirement is
satisfied; v7's direct-upload behavior is opt-in through `archive:
false`, which is not used.

The intended merge order is therefore one atomic merge of this PR; there
are no held upgrades or version twins left split across PRs.

## Validation

- `pnpm exec prettier --check .github/dependabot.yml
.github/actions/setup-workspace/action.yml .github/workflows/*.yml`
- Dependabot YAML parse and structural assertions for one update entry,
both directories, and the `*` group
- `pnpm exec turbo run build typecheck lint --cache-dir=.turbo/cache
--output-logs=new-only`
- `node apps/app/scripts/check-bundle-budget.mjs`
- all server tests: 1,468 passed
- all non-server Turbo test tasks: 54 passed
- `pnpm exec turbo run smoke:tarball --filter=bb-app
--cache-dir=.turbo/cache --output-logs=new-only`

The first all-at-once local test run had one unrelated server test
exceed its 15-second timeout under contention; the complete server shard
passed when rerun alone. PR CI will exercise `ci.yml` and
`version-lockstep.yml`. A safe `build-desktop.yml` branch dispatch will
separately exercise the macOS setup and artifact-upload path. The
publish, deploy, cache-restore, and credential-cleanup paths can only be
fully proven by their native GitHub-hosted runs.

> AGENT GENERATED: by GPT-5
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