-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade all packages to use Node.js v20 #132
Merged
Merged
Conversation
This file contains 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
… `generator-grow` with Node.js v20.
…mposing generators.
…ithub-actions` with Node.js v20.
…e to use Node.js v20.
…use Node.js v20.
…age to use Node.js v20.
…tor-grow Upgrade JS package `generator-grow` to use Node.js v20
Upgrade JS packages `jsdoc` and `tracking-jsdoc` to use Node.js v20
…`prepare-node`, and `update-version-tags` actions. Address: #112 (comment)
…-actions 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
… package to use Node.js v20.
…to use Node.js v20.
…l`, and `run-qit-annotate` actions to v2.
…e to use Node.js v20.
…kage to use Node.js v20.
…-actions-phpcs-diff Upgrade the `phpcs-diff` action to use Node.js v20
…-actions-linter Upgrade the `eslint-annotation` and `stylelint-annotation` actions to use Node.js v20
…age to use Node.js v20.
… easier to develop and test.
…e to use Node.js v20.
…nch with the test build of `run-qit-annotate`.
…ackage to use Node.js v20.
…` package to use Node.js v20.
…ns` package to use Node.js v20.
…-actions-get-plugin-releases Upgrade the `get-plugin-releases` action to use Node.js v20
…t PR branch with the test build of `run-qit-annotate`." This reverts commit f0b21e0.
This reverts commit 3f7ee00.
…-actions-run-qit-extension Upgrade the `run-qit-extension` action to use Node.js v20
…-actions-release-related Upgrade the `merge-trunk-develop-pr`, `prepare-extension-release`, and `publish-extension-dev-build` actions to use Node.js v20
…use Node.js v20.
…o the `branch-label` action in the `github-actions` package. Address: - #122 (comment) - #122 (comment)
…-actions-branch-label Upgrade the `branch-label` action to use Node.js v20
… `github-actions` package. Address: #123 (comment)
…-actions-docs Update the README for the `github-actions` package to be based on Node.js v20
… JS package `generator-grow`.
…tor-grow-upgrade-actions Upgrade the templates to use the latest versions of GitHub actions in the JS package `generator-grow`
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.
Changes proposed in this Pull Request:
It's a wrap-up PR for #108