Improve providers release docs: carry over testing-issue checkmarks + tag-providers --release-date#68228
Open
potiuk wants to merge 2 commits into
Open
Improve providers release docs: carry over testing-issue checkmarks + tag-providers --release-date#68228potiuk wants to merge 2 commits into
potiuk wants to merge 2 commits into
Conversation
…or re-cuts + tag-providers --release-date - document carrying over [x] checkmarks from the previous wave's testing issue when re-cutting held-back/cancelled providers (so testers don't re-verify unchanged code) - add the required --release-date to the tag-providers command examples
potiuk
requested review from
bugraoz93,
jedcunningham,
jscheffl,
shahar1 and
vincbeck
as code owners
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-2-test
The new 'carry over checkmarks' subsection used an h4 (####) directly under an h2, skipping h3. Demote to h3 (###) so heading levels only increment by one.
jscheffl
reviewed
Jun 8, 2026
|
|
||
| ```shell script | ||
| breeze release-management tag-providers | ||
| breeze release-management tag-providers --release-date ${RELEASE_DATE} |
Contributor
There was a problem hiding this comment.
I thought until now that the RELEASE_DATE is picked-up from ENV automatically via Shell?
jscheffl
approved these changes
Jun 8, 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.
Small improvements to the providers release process docs (
dev/README_RELEASE_PROVIDERS.md), found while running the 2026-06-08 wave:Carry over testing-issue checkmarks for re-cuts. When a provider is re-cut — held back from a previous wave and released again at
rc2/rc3, or a cancelled RC — the PRs already verified ([x]) in the previous wave's testing issue should stay checked in the new issue, so testers don't re-verify unchanged code; only genuinely new commits are left unchecked. Documents the extract-and-carry-over commands as a standard "always do this" step. (Applied live for 2026-06-08: issue carried the verified PRs over from the 2026-06-02 issue.)tag-providers --release-date. The command requires--release-date, but both examples showed it bare (breeze release-management tag-providers), which fails withMissing option '--release-date'. Fixed both examples.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines