shahar1 opened a new pull request, #68739:
URL: https://github.com/apache/airflow/pull/68739
The `prepare-providers-documentation` skill ended after regenerating the
provider build templates (Phase 4c) and handed control back to the regular
release workflow in `dev/README_RELEASE_PROVIDERS.md`. That left
`breeze release-management update-providers-next-version` — which resolves
inter-provider dependencies pinned with a `# use next version` comment to the
versions just bumped in the wave — entirely implicit.
Because that command sits between doc preparation and PR creation in the
release doc, it is easy to miss once the skill stops. When it is skipped the
wave merges with stale lower bounds on inter-provider dependencies, and the
only remedy after merge is a separate follow-up PR.
This adds it to the skill as an explicit step:
- **Phase 4d** — run `update-providers-next-version` after the templates are
regenerated and before the PR is opened, every time (it is a safe no-op
when no provider uses the comment).
- **Phase 5** — a validation bullet and a reminder in the closing note that
Phase 4d must have run before the PR is opened.
- **Incremental Phase 5** — re-run it when an incremental rebase bumps a
provider to a new version.
Docs-only change to an agent skill; no runtime code affected.
---
##### 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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
