Use RELEASE_DATE for the provider testing issue title - #72168
Merged
potiuk merged 1 commit intoAug 27, 2026
Conversation
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-3-test
o-nikolas
force-pushed
the
onikolas/testing-issue-honor-release-date
branch
2 times, most recently
from
August 27, 2026 19:16
d856de2 to
2fcac04
Compare
The title placeholder had to be filled in by hand, from today's date, even though the wave already has a date the release manager exported as RELEASE_DATE.
o-nikolas
force-pushed
the
onikolas/testing-issue-honor-release-date
branch
from
August 27, 2026 19:31
2fcac04 to
843d4f1
Compare
o-nikolas
marked this pull request as ready for review
August 27, 2026 19:31
o-nikolas
requested review from
bugraoz93,
jedcunningham,
jscheffl,
potiuk,
shahar1 and
vincbeck
as code owners
August 27, 2026 19:31
vincbeck
approved these changes
Aug 27, 2026
potiuk
approved these changes
Aug 27, 2026
Contributor
Backport successfully created: v3-3-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
github-actions Bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Aug 27, 2026
…ache#72168) The title placeholder had to be filled in by hand, from today's date, even though the wave already has a date the release manager exported as RELEASE_DATE. (cherry picked from commit e669196) Co-authored-by: Niko Oliveira <onikolas@apache.org>
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
3 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.
The testing-status issue title is
Status of testing Providers that were prepared on <date>, where the date identifies the wave. The documentedgh issue createcommand left it as a<MONTH DD, YYYY>placeholder to fill in by hand, so in practice it gets typed from today's date — which is not necessarily the wave's date. The two diverge whenever issue creation slips past midnight, or a wave is re-cut and the issue is regenerated a day later, leaving the issue naming a different wave than the one being tested and voted on.RELEASE_DATEis already exported by the release manager at the start of the process and is the canonical wave identifier, so this derives the title from it, stripping the optional_NNwave suffix. TheOSTYPEsplit follows the same pattern the vote-email step in this document already uses fordate.Tested: ran both branches' formatting locally —
2026-08-25and2026-08-25_01both yieldStatus of testing Providers that were prepared on August 25, 2026, byte-identical to the title of the issue created for the current wave (#72117) and to whatbreeze release-management generate-issue-content-providersprints.prek run --from-ref upstream/main --stage pre-commitis clean.Was generative AI tooling used to co-author this PR?
Generated-by: Kiro CLI (claude-fable-5) following the guidelines