chore(changelog): regenerate from conventional commits (final cleanup) - #222
Merged
Merged
Conversation
Final regeneration to pick up the loop-fix commit (#221) after its own [skip changelog] marker caused the workflow run to skip (which was the intended behavior to break the loop). No further changelog PRs should follow; see standards#988 for the canonical fix. [skip changelog]
|
Warning Review limit reachedNext included review available in 48 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
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 |
hyperpolymath
deleted the
fix/changelog-final-cleanup-20260922-160256
branch
September 22, 2026 16:04
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
1 participant
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.
One-line CHANGELOG update: adds the missing bullet for the loop-fix PR (#221) itself.
Why this PR exists
When #221 merged, its commit body contained the
[skip changelog]marker (added by the job-levelif:guard that broke the infinite loop), so the workflow run after merge correctly skipped itself rather than opening a regeneration PR. That was the right call for loop-prevention, but it means the fix commit itself was never recorded in the changelog. This PR adds that one bullet.Why this is the LAST changelog PR
Merging this PR will NOT open another changelog PR, because:
cliff.tomloverride (^chore\\(changelog\\):\\s*regenerate from conventional commits), so git-cliff will skip this commit when computing the next CHANGELOG.[skip changelog], which triggers both the caller's job-levelif:guard and the body-matcher skip rule in cliff.toml.The canonical fix in standards#988 applies the same skip rules to all estate repos. Once that merges, the local
cliff.tomlin this repo should be deleted in a follow-up.[skip changelog]