Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 20, 2025

This PR contains the following updates:

Package Type Update Change
actions/checkout action major v5 -> v6

Release Notes

actions/checkout (actions/checkout)

v6

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner November 20, 2025 18:04
@changeset-bot
Copy link

changeset-bot bot commented Nov 20, 2025

⚠️ No Changeset found

Latest commit: e712977

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 20, 2025

Walkthrough

The changes consistently update multiple GitHub Actions workflow files in the .github/workflows/ directory. Each workflow file has been modified to upgrade the actions/checkout action from version 5 to version 6. The files affected are: actionlint.yml, changeset.yml, checks.yml, docs.yml, formal-verification.yml, release-cycle.yml, and upgradeable.yml. This is a straightforward dependency version upgrade where all instances of actions/checkout@v5 are replaced with actions/checkout@v6. No other workflow logic, steps, or configuration details are altered.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: updating the actions/checkout action from v5 to v6 across multiple GitHub Actions workflows.
Description check ✅ Passed The description clearly relates to the changeset, providing a changelog table documenting the v5 to v6 update of actions/checkout with release notes and configuration details.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch renovate/actions-checkout-6.x

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0de8004 and e712977.

📒 Files selected for processing (7)
  • .github/workflows/actionlint.yml (1 hunks)
  • .github/workflows/changeset.yml (1 hunks)
  • .github/workflows/checks.yml (7 hunks)
  • .github/workflows/docs.yml (1 hunks)
  • .github/workflows/formal-verification.yml (2 hunks)
  • .github/workflows/release-cycle.yml (7 hunks)
  • .github/workflows/upgradeable.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)
  • GitHub Check: Redirect rules - solidity-contracts
  • GitHub Check: Header rules - solidity-contracts
  • GitHub Check: Pages changed - solidity-contracts
  • GitHub Check: coverage
  • GitHub Check: tests
  • GitHub Check: slither
  • GitHub Check: tests-upgradeable
  • GitHub Check: tests-foundry
  • GitHub Check: halmos
🔇 Additional comments (22)
.github/workflows/docs.yml (1)

14-14: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 is straightforward with no configuration parameters to verify compatibility.

.github/workflows/actionlint.yml (1)

12-12: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 is straightforward.

.github/workflows/upgradeable.yml (1)

14-18: Checkout action upgrade with configuration parameters looks good.

The upgrade to actions/checkout@v6 preserves all configuration parameters (repository, fetch-depth, token), which are backward-compatible across major versions.

.github/workflows/formal-verification.yml (3)

23-23: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the apply-diff job is straightforward.


31-33: Checkout action upgrade with fetch-depth parameter looks good.

The upgrade to actions/checkout@v6 in the verify job preserves the fetch-depth parameter, which is backward-compatible.


74-74: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the halmos job is straightforward.

.github/workflows/release-cycle.yml (7)

30-30: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the state job is straightforward.


61-61: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the start job is straightforward.


84-84: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the promote job is straightforward.


105-107: Checkout action upgrade with fetch-depth parameter looks good.

The upgrade to actions/checkout@v6 in the changesets job preserves the fetch-depth: 0 parameter for fetching all tags, which is backward-compatible.


138-138: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the publish job is straightforward.


170-170: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the integrity_check job is straightforward.


192-194: Checkout action upgrade with fetch-depth parameter looks good.

The upgrade to actions/checkout@v6 in the merge job preserves the fetch-depth: 0 parameter for fetching all branches, which is backward-compatible.

.github/workflows/changeset.yml (1)

22-24: Checkout action upgrade with fetch-depth parameter looks good.

The upgrade to actions/checkout@v6 preserves the fetch-depth: 0 parameter to include history for Changesets, which is backward-compatible.

.github/workflows/checks.yml (8)

23-23: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the lint job is straightforward.


37-37: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the tests job is straightforward.


58-60: Checkout action upgrade with fetch-depth parameter looks good.

The upgrade to actions/checkout@v6 in the tests-upgradeable job preserves the fetch-depth: 0 parameter for automatic conflict resolution with history, which is backward-compatible.


84-86: Checkout action upgrade with submodules parameter looks good.

The upgrade to actions/checkout@v6 in the tests-foundry job preserves the submodules: recursive parameter for fetching nested submodules, which is backward-compatible.


95-95: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the coverage job is straightforward.


107-107: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the harnesses job is straightforward.


118-118: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the slither job is straightforward.


126-126: Checkout action upgrade looks good.

The upgrade from actions/checkout@v5 to actions/checkout@v6 in the codespell job is straightforward.


Comment @coderabbitai help to get the list of available commands and usage tips.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant