chore: automate upgrading Node.js on cdktf-provider-project #337
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
xiehan
requested review from
ansgarm and
Maed223
and removed request for
a team
Signed-off-by: team-tf-cdk <[email protected]>
DanielMSchmidt
approved these changes
Oct 13, 2023
|
I'm going to lock this pull request because it has been closed for at least 7 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue so we can investigate further. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This uses the same script that's already been tested & proven to work well on hashicorp/cdktf-aws-cdk. Note that this only upgrades Node on the provider-project itself because the Node version used by the individual provider repos is managed by cdktf-repository-manager instead.
Also adds the automerge and auto-approve workflows we've been using elsewhere. We don't have to start using them, but this way these automations are there if/when we need them.