Repository navigation
release: Prepare v0.6.0 release notes - #162
Merged
Merged
Conversation
The v0.5.1 release PR (#157) archived v0.5.0's entries but not its own — pr-155.txt remained in .changelog/ and would be repeated in every future release's notes. Moves it to .changelog/archive/v0.5.1/. Co-Authored-By: Claude Code <noreply@anthropic.com>
Generates release-notes/v0.6.0/ (GITHUB_RELEASE.md + RELEASE_NOTES.adoc) covering the two changes since v0.5.1: - #159 — bare Terraform traversals in jsonencode blobs (tflint terraform_deprecated_interpolation fix) - #161 — secret DaVinci variables export with a variable-backed value block The pr-155 v0.5.1 archive ships in the preceding commit on this branch. Co-Authored-By: Claude Code <noreply@anthropic.com>
Regression Test Results
✅ No regressions detectedAll export configurations produced compatible output. Generated by regression workflow • View run |
This file contains hidden or 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.
Summary
Prepares the v0.6.0 minor release — the first release carrying both the bare-traversal output change (#159) and the secret-variable export fix (#161), which merged to
mainasaf64022andaa4e567.Release contents
jsonencode({...})blobs render as bare Terraform traversals instead of deprecated interpolation-only strings (fixes tflintterraform_deprecated_interpolationon exported modules)valueblock backed by a generatedsensitive = truevariable whose tfvars entry is empty (fill manually; plan fails on empty by design)Both changes recommend a re-export, so v0.6.0's notes give users one combined reason to re-export.
Housekeeping
pr-155) to.changelog/archive/v0.5.1/— the v0.5.1 release PR (release: Prepare v0.5.1 release notes #157) archived v0.5.0's entries but not its own, so the generator would have repeated pr-155 in every future release. This follows the established convention (each release's prep archives the previous release's entries; the current release's entries stay in.changelog/until the next release's prep).After merge
git tag v0.6.0 && git push origin v0.6.0— the goreleaser workflow builds and publishes onv*tags.Tests
Not applicable — release metadata only. No code changes. (Both content PRs' CI ran green: #159 all 8 checks, #161 regression suite; the combined tree was also verified locally before merging — 14/14 packages, only the known pre-existing map-order flake in
TestResolveEmbeddedReferences_DisambiguatedName_StableAcrossEnvironments, documented in #161.)Breaking changes
None. Both shipped changes are additive enhancements; #159's output change is semantically equivalent (interpolation-only vs bare traversal) and #161's new blocks/variables are additive.
🤖 Generated with Claude Code