Skip to content

Automate Release Notes Generation for airflowctl#65180

Merged
bugraoz93 merged 3 commits intoapache:mainfrom
bugraoz93:airflowctl-release-process-improvements
Apr 14, 2026
Merged

Automate Release Notes Generation for airflowctl#65180
bugraoz93 merged 3 commits intoapache:mainfrom
bugraoz93:airflowctl-release-process-improvements

Conversation

@bugraoz93
Copy link
Copy Markdown
Contributor

@bugraoz93 bugraoz93 commented Apr 13, 2026

Screencast.from.2026-04-13.23-17-25.mp4

Tested changes locally. They look good. Otherwise, this would be a lot of back and forth with git logs until ATR.

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)
    Claude Sonnet 4.6
  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch labels Apr 13, 2026
@bugraoz93
Copy link
Copy Markdown
Contributor Author

bugraoz93 commented Apr 13, 2026

Okay, it seems we already have breeze release-management generate-issue-content-airflow-ctl but never documented in the RELEASE doc. Will amend that part

@potiuk
Copy link
Copy Markdown
Member

potiuk commented Apr 13, 2026

Okay, it seems we already have breeze release-management generate-issue-content-airflow-ctl but never documented in the RELEASE doc. Will amend that part

It's been added literally two days ago ?

@bugraoz93
Copy link
Copy Markdown
Contributor Author

bugraoz93 commented Apr 13, 2026

Okay, it seems we already have breeze release-management generate-issue-content-airflow-ctl but never documented in the RELEASE doc. Will amend that part

It's been added literally two days ago ?

Yes and it is merged yesterday, should have missed this

@bugraoz93 bugraoz93 changed the title Automate Status Issue and Release Notes Generation for airflowctl Automate Release Notes Generation for airflowctl Apr 13, 2026
@bugraoz93
Copy link
Copy Markdown
Contributor Author

bugraoz93 commented Apr 13, 2026

Amended the changes and only kept the generating release notes. Also added the newly added to the release document

@bugraoz93
Copy link
Copy Markdown
Contributor Author

bugraoz93 commented Apr 13, 2026

Static checks failing will fix it before merge it, need to go to bed 😴

@eladkal eladkal added the changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..) label Apr 14, 2026
@bugraoz93 bugraoz93 force-pushed the airflowctl-release-process-improvements branch from a1b2068 to 35e118b Compare April 14, 2026 19:24
@bugraoz93
Automate Status Issue and Release Notes Generation for airflowctl
2804132
@bugraoz93
Clean up airflowctl release commands: keep only generate-airflowctl-c…
6935e62 
…hangelog

Remove the enhanced generate-issue-content-airflow-ctl overrides (version/
version-suffix/create-issue options, custom template) that duplicated work
already merged in apache#65042. Revert to the upstream command signature that uses
generate_issue_content(is_airflow_ctl=True).

Keep only the new generate-airflowctl-changelog command and its private
helpers (_get_airflowctl_prs, _build_changelog_content,
_prepend_changelog_to_release_notes) which prepend a categorised RST
changelog to airflow-ctl/RELEASE_NOTES.rst.
@bugraoz93
Amend breeze docs
52745e6
@bugraoz93 bugraoz93 force-pushed the airflowctl-release-process-improvements branch from 35e118b to 52745e6 Compare April 14, 2026 20:55
@bugraoz93
Copy link
Copy Markdown
Contributor Author

bugraoz93 commented Apr 14, 2026 •
edited
Loading

Failed again, but it shouldn't be related normally as mentioned in the provider toml update

https://github.com/apache/airflow/actions/runs/24418548499/job/71340274403?pr=65180

Rebased

@bugraoz93 bugraoz93 merged commit c3f1590 into apache:main Apr 14, 2026
135 of 137 checks passed
@bugraoz93 bugraoz93 deleted the airflowctl-release-process-improvements branch April 14, 2026 22:14
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 14, 2026

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
❌ v3-2-test Commit Link

You can attempt to backport this manually by running:

cherry_picker c3f1590 v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@potiuk potiuk potiuk approved these changes

@eladkal eladkal eladkal approved these changes

@jscheffl jscheffl Awaiting requested review from jscheffl jscheffl is a code owner

@vincbeck vincbeck Awaiting requested review from vincbeck vincbeck is a code owner

@shahar1 shahar1 Awaiting requested review from shahar1 shahar1 is a code owner

@jedcunningham jedcunningham Awaiting requested review from jedcunningham jedcunningham is a code owner

@ashb ashb Awaiting requested review from ashb ashb is a code owner

@gopidesupavan gopidesupavan Awaiting requested review from gopidesupavan gopidesupavan is a code owner

@amoghrajesh amoghrajesh Awaiting requested review from amoghrajesh amoghrajesh is a code owner

@jason810496 jason810496 Awaiting requested review from jason810496 jason810496 is a code owner

@ephraimbuddy ephraimbuddy Awaiting requested review from ephraimbuddy ephraimbuddy is a code owner

@choo121600 choo121600 Awaiting requested review from choo121600 choo121600 is a code owner

@vatsrahul1001 vatsrahul1001 Awaiting requested review from vatsrahul1001 vatsrahul1001 is a code owner

Assignees

No one assigned

Labels

area:dev-tools backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..)

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@bugraoz93 @potiuk @eladkal