docs: Bring CHANGELOG up to date for 0.12.0 - #248
Merged
Conversation
CHANGELOG.md stopped at 0.9.0 while tags ran to v0.11.0. Add 0.12.0 for the work now on main, and backfill the three releases that were missed, keeping the existing format and its level of detail -- dependency bumps summarised rather than enumerated, as in earlier entries. The 0.12.0 NOTES entry is the one worth reading: the provider has never sent metadata, so updates already cleared UI-set custom field values silently. That is now visible in the plan as an explicit removal. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
📝 WalkthroughWalkthroughUpdated Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This PR only adds historical release notes and does not alter product or runtime behavior. The remaining issues are limited to Markdown formatting consistency, so no actionable merge-blocking risk remains. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: d7c6d3a2-afe8-49cd-8648-e2ee2574cfc8
📒 Files selected for processing (1)
CHANGELOG.md
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.
khvn26
approved these changes
Aug 26, 2026
matthewelwell
added a commit
that referenced
this pull request
Aug 26, 2026
#248 brought the content up to date, so this is now purely a formatting change: convert every entry onto the headings release-please emits, so what it appends from here reads as one document. Bullet text is copied verbatim -- only headings, dates and compare links change. The three bare "fix https://..." lines under 0.5.1, 0.7.0 and 0.8.1 become bullets, same text. ENHANCEMENTS and NOTES keep their own headings rather than being forced into a release-please section that would change what they mean. 0.12.0 is dated 2026-08-26, the day #248 merged. It is not tagged yet, so correct the date if the release lands on another day. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
matthewelwell
added a commit
that referenced
this pull request
Aug 26, 2026
Releases were cut by hand-pushing a v* tag. Adopt release-please so the tag and release notes come from a release PR instead. No workflow: github-webhook-handler runs release-please itself on every push to the default branch, for any repo with both config files in its root. It deliberately stands down if it finds a .github/workflows/release-please*.yml (see should_run_release_please), so adding one would opt this repo out of the org mechanism rather than complement it. The flagship repos are all config-only; flagsmith-cli was migrated off its workflow in July. The handler tags using a GitHub App installation token, which does trigger workflows, so the existing goreleaser run still fires on the tag push -- flagsmith-cli releases the same way. goreleaser's release.mode is pinned to keep-existing so it attaches artifacts to the release the handler has already created rather than overwriting its notes. The manifest starts at 0.12.0, not 0.11.0, because #248 already wrote a 0.12.0 section by hand. Starting at 0.11.0 would have release-please propose 0.12.0 again and prepend a second section for it. bootstrap-sha points at that merge for the same reason. bump-minor-pre-major deviates from the value the other repos carry. They are all past 1.0.0, so it is inert for them; here it decides whether a breaking change bumps 0.12.0 to 0.13.0 or to 1.0.0. Every pre-1.0 breaking change in this provider so far (0.2.0, 0.3.0, 0.4.0) took the minor, and a Terraform registry version cannot be unpublished, so prefer the minor until 1.0.0 is a deliberate decision. Dependabot commits land as "Build(deps):", which fails the org PR title check outright (its regex requires a lowercase type) and is not a conventional commit type, so it would be dropped from the changelog. Set the prefix to "deps" to match the changelog-sections config. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
matthewelwell
added a commit
that referenced
this pull request
Aug 26, 2026
* docs: Put CHANGELOG into release-please format #248 brought the content up to date, so this is now purely a formatting change: convert every entry onto the headings release-please emits, so what it appends from here reads as one document. Bullet text is copied verbatim -- only headings, dates and compare links change. The three bare "fix https://..." lines under 0.5.1, 0.7.0 and 0.8.1 become bullets, same text. ENHANCEMENTS and NOTES keep their own headings rather than being forced into a release-please section that would change what they mean. 0.12.0 is dated 2026-08-26, the day #248 merged. It is not tagged yet, so correct the date if the release lands on another day. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * ci: Add release-please Releases were cut by hand-pushing a v* tag. Adopt release-please so the tag and release notes come from a release PR instead. No workflow: github-webhook-handler runs release-please itself on every push to the default branch, for any repo with both config files in its root. It deliberately stands down if it finds a .github/workflows/release-please*.yml (see should_run_release_please), so adding one would opt this repo out of the org mechanism rather than complement it. The flagship repos are all config-only; flagsmith-cli was migrated off its workflow in July. The handler tags using a GitHub App installation token, which does trigger workflows, so the existing goreleaser run still fires on the tag push -- flagsmith-cli releases the same way. goreleaser's release.mode is pinned to keep-existing so it attaches artifacts to the release the handler has already created rather than overwriting its notes. The manifest starts at 0.12.0, not 0.11.0, because #248 already wrote a 0.12.0 section by hand. Starting at 0.11.0 would have release-please propose 0.12.0 again and prepend a second section for it. bootstrap-sha points at that merge for the same reason. bump-minor-pre-major deviates from the value the other repos carry. They are all past 1.0.0, so it is inert for them; here it decides whether a breaking change bumps 0.12.0 to 0.13.0 or to 1.0.0. Every pre-1.0 breaking change in this provider so far (0.2.0, 0.3.0, 0.4.0) took the minor, and a Terraform registry version cannot be unpublished, so prefer the minor until 1.0.0 is a deliberate decision. Dependabot commits land as "Build(deps):", which fails the org PR title check outright (its regex requires a lowercase type) and is not a conventional commit type, so it would be dropped from the changelog. Set the prefix to "deps" to match the changelog-sections config. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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
2 participants
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.
Update CHANGELOG with missing versions, and (to be released after this is merged) 0.12.0.