Repository navigation
ci: upgrade actions/checkout and actions/setup-node to v7 - #25
Merged
Merged
Conversation
Contributor
|
Why did the migration stop at version 5 instead of continuing through version 7? |
Contributor
Author
Good point! I stopped at v5 initially just to fix the immediate Node runtime warning, but upgrading straight to the latest v7 makes total sense to stay fully up to date. I updated to v7. |
PaulFarault
approved these changes
Sep 29, 2026
6 of 10 tasks
Contributor
|
Please squash your commits before merging. We do not need to split those changes. |
alexismarie8314
force-pushed
the
ci/upgrade-actions-v5
branch
from
September 29, 2026 13:24
e653a56 to
0a397b4
Compare
alexismarie8314
force-pushed
the
ci/upgrade-actions-v5
branch
from
September 29, 2026 13:43
0a397b4 to
a694c01
Compare
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
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.
Description
Changes are proposed to fix the warning message in the Github Actions pipeline :
Related Issue
No related issue.
Type of Change
How to Test
Checklist