Prepare for v4.18.4 release #3352
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
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.
Changed
punycodedeprecation warnings by using nativefetchinstead ofnode-fetch.(The
punycodemodule is deprecated. Please use a userland alternative instead. #3301)Fixed
pulumi.com/waitForand other await annotations now correctly take precedence over default await logic.(StatefulSet update doesn't wait for pods to initialize #3329)
JSONPath expressions used with the
pulumi.com/waitForannotation will no longer hang indefinitely if they match non-primitive fields.(
pulumi.com/waitForannotation will hang when matching objects or arrays #3345)[java] CRDs that contain any
x-kubernetes-*fields can now be succesfully created and managed by Pulumi.(Issue with x_kubernetes_preserve_unknown_fields in java com.pulumi.kubernetes.apiextensions.v1.CustomResourceDefinition #3325)