chore(ci): upgrade checkout to v5 #198
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
touses: 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