Conversation
PR Summary
|
| }, | ||
| "engines": { | ||
| "node": ">=18.0.0 <19.0.0" | ||
| "node": ">=18.12.0 <19.0.0" |
There was a problem hiding this comment.
Is this a requirement of the new CDK version? Otherwise, I'd leave it as 18.0.0 in order to be less restrictive for end users.
There was a problem hiding this comment.
@javiertoledo yes, it seems to be a requirement for the new cdk tf version, see here. If it presents an issue, we can go back to version 0.17 I believe
There was a problem hiding this comment.
Gotcha, no objections then!
# Conflicts: # common/config/rush/pnpm-lock.yaml
|
/integration sha=4fc7a593c0f67fb95cded6defbb905c8e2b00c0b |
|
Oops, looks like you forgot to add a changeset.
This command will prompt you for a change description and generate a changeset file. You can read more about changesets here. Remember that you should use the version bump that is appropriate for the change you are making:
If you are unsure about which version bump to use, please ask in the comments and we will help you out. |
|
❌ Oh no! Integration tests have failed |
|
It seems that the Azure deployment failed. Maybe there's an API change that needs to be tweaked? |
I suspect it might have to do with rush running the build on 18.18, I've updated it to 18.20, hopefully that fixes it @javiertoledo |
|
Actually that broke it! Looking at it again. |
|
@javiertoledo I think we can try running integration tests now |
Description
Upgrade CDK TF to latest version
Changes
cdktf,cdktf-cli,@cdktf/provider-azurermand@cdktf/provider-timeto the latest version>=18.12.0 < 19.0.0wherevercdktf*packages are usedChecks
Additional information
If it's an issue moving to node
>=18.12.0 <19.0.0then wen move back to cdktf versions 18.x