Changelog for v2.3.6 release #318
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.
Similar to the recently reported hashicorp/terraform-provider-random#663 issue where the
v3.7.0-alpha1release had no protocol metadata, the cloudinitv2.3.6-alpha1release has no protocol metadata.The impact of that is only immediately apparent for TF
v0.12.31practitioners who are not pinning their provider versions, which will automatically grab pre-releases, see hashicorp/terraform#36586.This PR introduces a changelog for a
v2.3.6release, which will use the old Goreleaser process, and adjusts the release metadata file name to avoid running into a similar problem when we renamed it for CRT inrandom, see https://github.com/hashicorp/terraform-provider-random/actions/runs/13526648642/job/37798856402#step:9:78