[PR] Fix breeze provider release tooling (uvx paths, issue submission) [airflow]

["potiuk (via GitHub)" <gi...@apache.org>]

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

   Three fixes to the breeze provider-release tooling, all hit while cutting a
   providers release with breeze running via the uvx shim (the standard execution
   mode, see ADR 0017):
   
   - **`tag-providers` crashed under uvx** (`FileNotFoundError`). `SOURCE_DIR_PATH`
     walked the parents of the module's file, which under uvx resolves into the uv
     cache rather than the repo. It now derives from `AIRFLOW_ROOT_PATH`, and
     `tag-providers` reads `dist/` via `AIRFLOW_DIST_PATH` — so it works regardless
     of how breeze is launched. (Also fixes the latent `cwd=` and airflow-ctl
     `RELEASE_NOTES.rst` paths that used the same broken constant.)
   
   - **`generate-issue-content-providers` pulled in the wrong provider.**
     `is_package_in_dist` matched the provider id as a bare prefix, so `git` matched
     `apache_airflow_providers_github-*` — a `git` section appeared in the testing
     issue when only `github` was released. Now requires a trailing separator (same
     fix in `get_suffix_from_package_in_dist`).
   
   - **Issue submission was unreliable for large waves.** The issue was created with
     `gh issue create -b <body> -w`, which encodes the whole body into a URL and
     fails with "URL too long" on a 30+ provider wave, while the rich preview
     truncated at terminal width. The body is now written to a file (a temp file by
     default, or `--output-file <path>`) and submitted with `gh issue create
     --body-file`, so submission is reliable and the file is a deterministic artifact
     a human or agent can submit/re-submit. Added `--answer` for non-interactive runs.
   
   Adds breeze unit tests for the `git`/`github` matching and updates
   `dev/README_RELEASE_PROVIDERS.md` for the new file-based submission flow.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 4.8)
   
   Generated-by: Claude Code (Opus 4.8) 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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Fix breeze provider release tooling (uvx paths, issue submission) [airflow]

["potiuk (via GitHub)" <gi...@apache.org>]

potiuk merged PR #67960:
URL: https://github.com/apache/airflow/pull/67960


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Fix breeze provider release tooling (uvx paths, issue submission) [airflow]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on PR #67960:
URL: https://github.com/apache/airflow/pull/67960#issuecomment-4616743512

   ### Backport failed to create: v3-2-test. View the failure log <a href='https://github.com/apache/airflow/actions/runs/26913086721'> Run details </a>
   
   Note: As of [Merging PRs targeted for Airflow 3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   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](https://apache-airflow.slack.com/archives/C03G9H97MM2) Slack channel.
   
   <table>
       <tr>
           <th>Status</th>
           <th>Branch</th>
           <th>Result</th>
       </tr>
       <tr>
           <td>❌</td>
           <td>v3-2-test</td>
           <td><a href="https://github.com/apache/airflow/commit/dcb5cc57824650e8a0cb194e907c95d392b7d5a9"><img src='https://img.shields.io/badge/Commit-dcb5cc5-red' alt='Commit Link'></a></td>
       </tr>
   </table>
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker dcb5cc5 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:
   
   ```bash
   cherry_picker --continue
   ```
   
   If you don't have cherry-picker installed, see the [installation guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org