Remove dead airflow-ctl/newsfragments directory (unused by changelog tooling)#65507
Merged
Merged
Conversation
eladkal
approved these changes
Apr 19, 2026
bugraoz93
approved these changes
Apr 19, 2026
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.
airflow-ctl/newsfragments/contained aconfig.tomldeclaring towncrier categories, but thebreeze release-management generate-airflowctl-changelogcommand does not consume newsfragments — it builds the changelog section directly fromgit logoverairflow-ctl/. Contributors adding*.significant.rst/*.bugfix.rstfragments there never saw them show up in a release, and stale fragments (e.g. the59850.significant.rstfrom 0.1.2 that survived until the 0.1.4 cleanup) silently misled anyone reading the folder.Rather than wire up a second changelog pipeline, this PR removes the dead directory outright so the folder's existence stops implying a contract the tooling does not honour. If we later decide to switch to fragment-based changelogs, we can reintroduce the folder alongside the tooling change.
No runtime or doc code referenced this folder — the only documentation mention is in
dev/README_RELEASE_AIRFLOWCTL.mdwhich already notes that the generator does not consume newsfragments.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Opus 4.7 (1M context) following the guidelines