Clarify 'Fixing released docs' section to cover failed initial publish#66253
Merged
potiuk merged 1 commit intoMay 2, 2026
Merged
Conversation
jscheffl
reviewed
May 2, 2026
jscheffl
approved these changes
May 2, 2026
potiuk
approved these changes
May 2, 2026
Contributor
Backport successfully created: v3-2-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
May 2, 2026
…itial publish case (apache#66253) (cherry picked from commit 865718c) Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
aws-airflow-bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
May 2, 2026
…itial publish case (apache#66253) (cherry picked from commit 865718c) Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
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
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.
related: #66250
Clarifies the existing
## Fixing released documentationsection indev/README_RELEASE_PROVIDERS.mdto explicitly cover a second scenario: thepublish-docs-to-s3.ymlworkflow failing because a file it references orexecutes is missing or has incompatible logic in the release tag (e.g. it was
added or changed in
mainafter the tag was cut).Previously the section only mentioned post-publish fixes (typos, layout, etc.)
and did not explain the failed-initial-publish case, leaving release managers
without guidance when the workflow fails for this reason.
Changes:
## Fixing released documentationto list two distinctscenarios (post-publish fix vs. failed initial publish).
[!NOTE]callout in both the staging and livepublish-docssectionspointing to the
Fixing released documentationsection when the workflow failsdue to tag/file incompatibility.
Was generative AI tooling used to co-author this PR?
Generated-by: GitHub Copilot (Claude Sonnet 4.6) following the guidelines