Repository navigation
chore(docs): bump 26.9 pdfTag to v26.9.1 - #10235
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
automation/docs-version-26.9
branch
2 times, most recently
from
October 16, 2026 01:31
491d170 to
d553f6b
Compare
github-actions
Bot
force-pushed
the
automation/docs-version-26.9
branch
from
October 16, 2026 06:58
d553f6b to
631044f
Compare
This branch has not been deployed
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.
Automated by docs-version-pdftag-pr.yml (FR-3246) on release v26.9.1.
Bumps the existing 26.9 entry's pdfTag in docs-toolkit.config.yaml so the docs site's 26.9 version links the v26.9.1 release PDFs. latest: is untouched.
Merging this PR triggers the docs Amplify rebuild. The archived docs source is seeded/refreshed separately by docs-archive-orphan-branch.yml on the same release.
Note: PRs opened by GITHUB_TOKEN do not spawn Actions check runs, so required checks may show as pending; merge with admin if branch protection blocks.