Skip to content

Conversation

rejected-l
Copy link

@rejected-l rejected-l commented Aug 12, 2025

GitHub-hosted runners now use Node 24, so actions/checkout@v5 is required. Minimum runner version v2.327.1. Workflows only updated—no functional changes.

See: https://github.com/actions/checkout/releases/tag/v5.0.0

Greptile Summary

This PR performs a routine maintenance upgrade of the actions/checkout GitHub Action from version 4 to version 5 across all workflow files in the repository. The upgrade is driven by GitHub's infrastructure update where GitHub-hosted runners now use Node.js 24, making checkout@v5 a mandatory requirement for compatibility (minimum runner version v2.327.1).

The changes span five workflow files:

  • .github/workflows/publish-bolt-crates.yml (3 instances updated)
  • .github/workflows/publish-bolt-sdk.yml (3 instances updated)
  • .github/workflows/publish-packages.yml (3 instances updated)
  • .github/workflows/run-tests.yml (2 instances updated)
  • .github/workflows/run-lint.yml (2 instances updated)

Each change is identical - simply updating uses: actions/checkout@v4 to uses: actions/checkout@v5. The upgrade maintains full backward compatibility while ensuring workflows continue to function on GitHub's updated runner infrastructure. This is a standard CI/CD maintenance task that prevents potential workflow failures when GitHub updates their hosted runners. All workflow logic, job dependencies, and functionality remain unchanged.

Confidence score: 5/5

  • This PR is extremely safe to merge with virtually no risk of issues
  • Score reflects simple version updates with no logic changes and mandatory compatibility requirements
  • No files require special attention as all changes are identical version bumps

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

5 files reviewed, no comments

Edit Code Review Bot Settings | Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants