shahar1 opened a new pull request, #70358:
URL: https://github.com/apache/airflow/pull/70358

   This updates provider release issue generation to handle changelog bullets 
that reference more than one PR (for example: ).\n\nWithout this, release 
testing issues can miss substantial provider changes even when they are present 
in the changelog.\n\nWhat changed:\n- Extract all PR references from each 
changelog bullet in \n- Apply the same multi-PR extraction to 
excluded/commented changelog sections\n- Add regression tests for both multi-PR 
cases\n\nValidation:\n- ============================= test session starts 
==============================
   platform linux -- Python 3.13.0, pytest-9.1.1, pluggy-1.6.0 -- 
/home/shahar/repos/apache/airflow/dev/breeze/.venv/bin/python3
   cachedir: .pytest_cache
   rootdir: /home/shahar/repos/apache/airflow/dev/breeze
   configfile: pyproject.toml
   plugins: xdist-3.8.0, anyio-4.14.2
   collecting ... collected 36 items
   
   
dev/breeze/tests/test_release_management_commands.py::test_is_initial_provider_release[provider_yaml_dict0-True]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_is_initial_provider_release[provider_yaml_dict1-False]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_is_initial_provider_release[provider_yaml_dict2-False]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_is_initial_provider_release[None-False]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_should_include_provider_in_issue[provider_yaml_dict0-prs_for_current_release0-prs_after_exclusions0-True]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_should_include_provider_in_issue[provider_yaml_dict1-prs_for_current_release1-prs_after_exclusions1-True]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_should_include_provider_in_issue[provider_yaml_dict2-prs_for_current_release2-prs_after_exclusions2-False]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_should_include_provider_in_issue[provider_yaml_dict3-prs_for_current_release3-prs_after_exclusions3-False]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_get_prs_from_git_log_for_new_provider
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_get_prs_for_package_extracts_multiple_prs_per_line
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_get_commented_out_prs_extracts_multiple_prs_per_line
 [info]Checking changelog 
/tmp/pytest-of-shahar/pytest-2/test_get_commented_out_prs_ext0/changelog.rst 
for PRs to be excluded automatically.
   PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_release_management_commit_pattern[Prepare
 provider documentation 2026-06-16 (#68642)-True] PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_release_management_commit_pattern[Prepare
 providers release 2026-06-08 (#68203)-True] PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_release_management_commit_pattern[Prepare
 Providers Release 2026-06-08 (#1)-True] PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_release_management_commit_pattern[Prepare
 provider's documentation (#2)-True] PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_release_management_commit_pattern[Prepare
 ad-hoc RC2 providers release (#3)-True] PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_release_management_commit_pattern[Prepare
 documentation for next release of providers (#4)-True] PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_release_management_commit_pattern[Prepare
 bteq command with subprocess arg list (#67999)-False] PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_release_management_commit_pattern[Add
 ClickHouse Provider (#67080)-False] PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_release_management_commit_pattern[Bump
 `clickhouse-connect>=1.3.0` (#68400)-False] PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_get_prs_from_git_log_for_new_provider_returns_empty_on_git_failure
 Could not retrieve git history for provider clickhousedb: fatal: bad 
revision
   PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_ensure_default_python_for_reproducible_client_passes_on_default
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_ensure_default_python_for_reproducible_client_exits_on_mismatch[3.11]
 Python version mismatch: current version is 3.11, but 
the reproducible client must be built 
   with Python 3.10.
   Please rerun breeze with Python 3.10.
   
     - For the recommended uvx-based setup, set UV_PYTHON before invoking 
breeze:
           UV_PYTHON=3.10 breeze ...
     - For a legacy global install, reinstall with the right Python:
           uv tool install --python 3.10 -e 
./dev/breeze --force
   
   PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_ensure_default_python_for_reproducible_client_exits_on_mismatch[3.13]
 Python version mismatch: current version is 3.13, but 
the reproducible client must be built 
   with Python 3.10.
   Please rerun breeze with Python 3.10.
   
     - For the recommended uvx-based setup, set UV_PYTHON before invoking 
breeze:
           UV_PYTHON=3.10 breeze ...
     - For a legacy global install, reinstall with the right Python:
           uv tool install --python 3.10 -e 
./dev/breeze --force
   
   PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_ensure_default_python_for_reproducible_client_exits_on_mismatch[3.9]
 Python version mismatch: current version is 3.9, but 
the reproducible client must be built 
   with Python 3.10.
   Please rerun breeze with Python 3.10.
   
     - For the recommended uvx-based setup, set UV_PYTHON before invoking 
breeze:
           UV_PYTHON=3.10 breeze ...
     - For a legacy global install, reinstall with the right Python:
           uv tool install --python 3.10 -e 
./dev/breeze --force
   
   PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_is_package_in_dist[dist_files0-git-False]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_is_package_in_dist[dist_files1-github-True]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_is_package_in_dist[dist_files2-apache.spark-True]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_is_package_in_dist[dist_files3-git-True]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_is_package_in_dist[dist_files4-git-False]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_get_suffix_from_package_in_dist[dist_files0-git-None]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_get_suffix_from_package_in_dist[dist_files1-github-rc1]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_get_suffix_from_package_in_dist[dist_files2-git-rc2]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_get_suffix_from_package_in_dist[dist_files3-apache.spark-]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_get_package_version_possibly_from_stable_txt_for_java_sdk[None-None]
 PASSED
   
dev/breeze/tests/test_release_management_commands.py::test_get_package_version_possibly_from_stable_txt_for_java_sdk[0.1.0\n-0.1.0]
 PASSED
   
   ============================== 36 passed in 0.19s 
==============================\n- All checks passed!\n- 2 files left 
unchanged\n\nRelated: #69562\n\n---\n\n##### Was generative AI tooling used to 
co-author this PR?\n\n- [X] Yes — GitHub Copilot 
(GPT-5.3-Codex)\n\nGenerated-by: GitHub Copilot (GPT-5.3-Codex) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to