potiuk opened a new pull request, #71836:
URL: https://github.com/apache/airflow/pull/71836
When review concludes that an already-prepared provider has no user-facing
changes, correcting its
changelog entry is not enough: the version bump and the changelog section
stay behind, so the provider
is still built and uploaded to PyPI. Undoing that by hand is a restore →
re-run → answer-`N` sequence
that release managers repeatedly get wrong, and the sequence was documented
nowhere outside the breeze
sources.
It is also unreachable during an incremental update. `--incremental-update`
calls
`set_forced_answer("yes")`, which makes `user_confirm` answer every prompt
with yes — including
`Do you want to leave the version for X as is?`, the gate behind the
existing reclassify-to-doc-only
path. So at the point in the release where this decision is actually made,
it could not be applied at all.
This adds a single command for it:
```shell script
breeze release-management prepare-provider-documentation --mark-doc-only
PROVIDER [MORE PROVIDERS]
```
It restores the provider's `provider.yaml` and `changelog.rst` to their
released state and records
`docs/.latest-doc-only-change.txt` for you to commit. It reuses the existing
doc-only marking path, so
these providers appear in the usual doc-only summary bucket. It requires an
explicit provider list —
it takes providers out of a release, so defaulting to all of them would be
the wrong failure mode —
and it refuses to write an empty marker when there is nothing to mark, since
a bad marker would
silence that provider's next release too.
Documentation is added for both flows: the release guide gains a section
explaining the difference
between a `doc-only` changelog entry (package still ships) and the marker
file (no PyPI artifact at
all), and the `prepare-providers-documentation` skill gains the matching
case in its pre-merge sweep —
which until now only looked for providers *missing* from a wave, never for
providers that should no
longer be in one.
Raised on devlist Slack by the provider release managers.
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Opus 5)
Generated-by: Claude Code (Opus 5) 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]
