Skip to content

Include multi-PR changelog entries in provider issue generation - #70358

Merged
shahar1 merged 1 commit into
apache:mainfrom
shahar1:fix-kafka-provider-issue-pr-extraction
Jul 24, 2026
Merged

Include multi-PR changelog entries in provider issue generation#70358
shahar1 merged 1 commit into
apache:mainfrom
shahar1:fix-kafka-provider-issue-pr-extraction

Conversation

@shahar1

@shahar1 shahar1 commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

This updates provider release issue generation to handle changelog bullets that reference more than one PR (for example: (#68082, #70014)).

Without this, release testing issues can miss substantial provider changes even when they are present in the changelog.

What changed:

  • Extract all PR references from each changelog bullet in get_prs_for_package
  • Apply the same multi-PR extraction to excluded/commented changelog sections
  • Add regression tests for both multi-PR cases

Validation:

  • uv run --project dev/breeze pytest dev/breeze/tests/test_release_management_commands.py -xvs
  • uv run ruff check --fix dev/breeze/src/airflow_breeze/commands/release_management_commands.py dev/breeze/tests/test_release_management_commands.py
  • uv run ruff format dev/breeze/src/airflow_breeze/commands/release_management_commands.py dev/breeze/tests/test_release_management_commands.py

Related: #69562


Was generative AI tooling used to co-author this PR?
  • Yes — GitHub Copilot (GPT-5.3-Codex)

Generated-by: GitHub Copilot (GPT-5.3-Codex) following the guidelines

Provider release issue generation was missing changelog bullets that reference more than one PR, which hid substantial changes from contributor testing checklists. This keeps release wave issue content aligned with changelog intent by extracting every PR reference from each bullet and from excluded changelog sections.
@shahar1
shahar1 merged commit 04fd3a9 into apache:main Jul 24, 2026
301 of 302 checks passed
@shahar1
shahar1 deleted the fix-kafka-provider-issue-pr-extraction branch July 24, 2026 13:19
@github-actions

Copy link
Copy Markdown
Contributor

Backport failed to create: v3-3-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-3-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 04fd3a9 v3-3-test

This should apply the commit to the v3-3-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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants