Upgrade the fundamental of the github-actions
package and its get-release-notes
, prepare-node
, and update-version-tags
actions to use Node.js v20
#112
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.
Changes proposed in this Pull Request:
Part of #108
This PR:
github-actions
with Node.js v20.">=18"
, which aligns with the dependencies' minimum ([email protected]
).github-actions
package to use Node.js v20.get-release-notes
action.prepare-node
action.update-version-tags
action.💡 Other actions will be upgraded in subsequent PRs.
💡 The
<repo_directory>/.nvmrc
and other GitHub Actions workflows will be updated in a separate PR.Detailed test instructions:
This PR involves the release processing of the
github-actions
package. It can only be verified after merging it totrunk
. Therefore, I tested it with a forked repo.github-actions
to use Node.js v20 eason9487/grow#14github-actions
package.github-actions
package eason9487/grow#15actions-v2
,actions-v2.0
, andactions-v2.0.0
tags were created and pointed to the same revision. Theactions-v1
andactions-v1.*
tags were not changed.