fix(ci): upgrade actions/checkout from v2 to v6.0.2 with SHA pinning#172
Merged
fix(ci): upgrade actions/checkout from v2 to v6.0.2 with SHA pinning#172
Conversation
added 2 commits
April 30, 2026 21:12
- Update tests.yaml: v2 -> v6.0.2 (lines 12, 82) - Update release.yaml: v4.2.2 -> v6.0.2 (line 17) - Use SHA pinning for supply chain security Fixes #148
DateInterval::createFromDateString() throws DateMalformedIntervalStringException on invalid input since PHP 8.2, so the try-catch block already handles errors. The assert() calls were redundant and caused PHPStan errors: - Call to function assert() with true will always evaluate to true - Instanceof between DateInterval and DateInterval will always evaluate to true
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
actions/checkoutfrom deprecated v2 to latest v6.0.2tests.yamlwithrelease.yamlpinning strategyChanges
tests.yaml: v2 → v6.0.2 (lines 12, 82)release.yaml: v4.2.2 → v6.0.2 (line 17)Security Impact
Fixes #148