feat!: update imports for K8s 1.27 #64
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
mrliptontea
force-pushed
the
chore_update_dependencies
branch
from
07e70e2
to
9f38d4b
Compare
mrliptontea
changed the title
stephenrob
approved these changes
Sep 4, 2023
kiyanwang
approved these changes
Sep 4, 2023
|
🎉 This PR is included in version 4.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 4.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
test/test.d.ts.typeRoots,include, andexcludewere incorrect in tsconfig, so removed them, as default values seem to work better.cdk8s importno longer generates enums from schema - I can't find any related issues but anyway I decided to include our own enums for the string values but not actually forcing them in types, because 1) underlying objects use string, and 2) there may be nested properties, for exampleinitContainers, that use imported types directly, so we can't control whether they require enums or not.