potiuk opened a new pull request, #72728: URL: https://github.com/apache/airflow/pull/72728
…elease (#71836) * Document dropping a prepared provider back to doc-only Release managers hit this when review concludes a prepared provider's changes are internal after all: the changelog entry can be corrected, but the version bump and changelog section stay behind and the provider is still built and uploaded. The sequence that actually removes it from the wave - and the marker file that records it - was described nowhere outside the breeze sources. The pre-merge sweep only ever looked for providers missing from a wave, so the opposite direction had nothing watching it in either the manual or the agentic flow. * Add a command to take a prepared provider back out of a release When review concludes that an already-prepared provider has no user-facing changes, correcting its changelog entry leaves the version bump and the changelog section behind, so the provider is still built and uploaded. Undoing that by hand is a restore-rerun-answer-N sequence that release managers repeatedly get wrong, and it is unavailable during an incremental update at all: that mode answers every question with yes, so the prompt that reclassifies a provider as doc-only never appears. * Say why a never-released provider cannot be dropped to doc-only Review pointed out that such a provider gets no doc-only marker. Writing one would not help: the marker is only read once the current version is tagged, so for a first release it is inert, and read literally it would suppress that release for good. What was wrong is the message, which claimed there were no changes when the real reason is that there is no earlier release to diff against. Marking the two functions that always raise as NoReturn also lets the compiler, rather than the reader, establish that the loop cannot continue past the doc-only branch. * Refresh the breeze command hash for prepare-provider-documentation The committed hash was computed against a stale cached breeze build, so CI's static checks regenerated it and failed the run. (cherry picked from commit 391578af62027fe8939ad4bd6188eabcc6707f92) Generated-by: Claude Code (Opus 5) Claude-Session: https://claude.ai/code/session_01XS3bodTDYYGrPmorhtLsjP <!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Thank you for contributing! Please provide above a brief description of the changes made in this pull request. Write a good git commit message following this guide: https://chris.beams.io/posts/git-commit/ Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. For user-facing UI changes, please attach before/after screenshots (or a short screen recording) so reviewers can assess the visual impact. Feel free to ping (in general) for the review if you do not see reaction for a few days (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: * closes: #ISSUE * related: #ISSUE --> --- ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [ ] Yes (please specify the tool below) <!-- Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --> --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#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](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- 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]
