Add update-providers-next-version step to provider docs skill#68739
Merged
shahar1 merged 2 commits intoJun 19, 2026
Conversation
The prepare-providers-documentation skill stopped after regenerating the build templates and handed back to the regular release workflow, leaving 'breeze release-management update-providers-next-version' implicit. That step resolves inter-provider dependencies pinned with '# use next version' to the just-released versions and must run before the PR is opened; missing it ships the wave with stale lower bounds and needs a follow-up PR to fix. Make the skill run it as an explicit phase and check for it during validation.
Reflect in README_RELEASE_PROVIDERS.md that the prepare-providers-documentation skill now runs update-providers-next-version itself, and that an incremental update which bumps a version must re-run that step on the rebased branch — for both the skill and the interactive breeze flows.
shahar1
requested review from
bugraoz93,
jedcunningham,
jscheffl and
vincbeck
as code owners
1 task
amoghrajesh
approved these changes
Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Human Summary
It turns out that I've missed running "update-providers-next-version" while using the prepare-docs skill in #68642.
This PR fixes it.
AI Summary
Click here
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:
update-providers-next-versionafter the templates areregenerated and before the PR is opened, every time (it is a safe no-op
when no provider uses the comment).
Phase 4d must have run before the PR is opened.
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?
Generated-by: Claude Code (Opus 4.8) following the guidelines