chore: add changelog fragment to unstick versioning#3475
Merged
Conversation
The #3471 revert removed the only pending fragment, so towncrier now exits non-zero ("No changelog fragments found") on every push and the Deploy API + Docker jobs stay skipped. Ship a no-op fragment so the next push triggers a clean versioning + deploy cycle. Co-Authored-By: Claude Opus 4.7 (1M context) <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
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.
Summary
The #3471 revert (#3473) removed the only pending changelog fragment, so towncrier now exits non-zero with "No changelog fragments found" on every push to master — the versioning job fails and Deploy API + Docker jobs stay skipped. Ship a no-op fragment so the next push triggers a clean versioning + deploy cycle.
No functional change. After merge the versioning bot will consume this fragment, bump the version, and restore the normal deploy pipeline.
Unrelated: CI failures on "Test environment variables" are pre-existing (same
gov.contrib.additional_tax_bracket.bracket.ratesmetadata error that's also failing onauto/update-policyengine-us-1.653.*), not introduced by this PR.🤖 Generated with Claude Code