Skip to content

Clarify 'Fixing released docs' section to cover failed initial publish#66253

Merged
potiuk merged 1 commit into
apache:mainfrom
shahar1:fix/clarify-fixing-released-docs-section
May 2, 2026
Merged

Clarify 'Fixing released docs' section to cover failed initial publish#66253
potiuk merged 1 commit into
apache:mainfrom
shahar1:fix/clarify-fixing-released-docs-section

Conversation

@shahar1
Copy link
Copy Markdown
Contributor

@shahar1 shahar1 commented May 2, 2026

related: #66250


Clarifies the existing ## Fixing released documentation section in
dev/README_RELEASE_PROVIDERS.md to explicitly cover a second scenario: the
publish-docs-to-s3.yml workflow failing because a file it references or
executes is missing or has incompatible logic in the release tag (e.g. it was
added or changed in main after 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:

  • Rewrote the intro of ## Fixing released documentation to list two distinct
    scenarios (post-publish fix vs. failed initial publish).
  • Added a [!NOTE] callout in both the staging and live publish-docs sections
    pointing to the Fixing released documentation section when the workflow fails
    due to tag/file incompatibility.

Was generative AI tooling used to co-author this PR?
  • Yes — GitHub Copilot (Claude Sonnet 4.6)

Generated-by: GitHub Copilot (Claude Sonnet 4.6) following the guidelines

@boring-cyborg boring-cyborg Bot added area:dev-tools backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch labels May 2, 2026
Comment thread dev/README_RELEASE_PROVIDERS.md
@potiuk potiuk merged commit 865718c into apache:main May 2, 2026
64 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 2, 2026

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-2-test PR Link

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>
potiuk pushed a commit that referenced this pull request May 2, 2026
…itial publish case (#66253) (#66271)

(cherry picked from commit 865718c)

Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants