Repository navigation
fix(ci): snapshot release docs from release tag (backport #1802) - #1808
Merged
ajbozarth merged 1 commit intoNov 11, 2026
Merged
Conversation
…#1802) * fix(ci): snapshot release docs from release tag The snapshot-docs job built each release's versioned docs from main, so they included unreleased changes. Build them from the release tag and land them on main through a sync PR instead. Also remove release triggers and dispatches made redundant by the app token switch in generative-computing#1376, and resolve the zizmor findings in generative-computing#1534. Assisted-by: Claude Code Signed-off-by: Alex Bozarth <ajbozart@us.ibm.com> * docs: explain how docs fixes reach release snapshots Snapshots are now built from the release tag, so a fix to a published snapshot must be made on main to deploy and also landed on the release branch to carry into the next patch's snapshot. Assisted-by: Claude Code Signed-off-by: Alex Bozarth <ajbozart@us.ibm.com> * fix(ci): address review feedback on release scripts Assisted-by: Claude Code Signed-off-by: Alex Bozarth <ajbozart@us.ibm.com> --------- Signed-off-by: Alex Bozarth <ajbozart@us.ibm.com>
ajbozarth
added
the
chore
ajbozarth
added
chore
ajbozarth
merged commit Nov 11, 2026
67a1cd5
into
generative-computing:release/v0.9
17 of 21 checks passed
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.
Issue
Backport of #1802 to
release/v0.9(original fixes #1534 and #1437)Description
Cherry-pick of #1802 (merge commit 0a087a2) onto
release/v0.9, whichpublish-releaseneeds before 0.9.0 because it runs the release branch's copy of the workflow. It applied cleanly with no conflicts.Every file #1802 touches is now identical to
main, exceptdispatch-to-contribs.yml. That file differs only by #1731's version validation and--raw-fieldchange, which isn't onrelease/v0.9and isn't needed for this fix; #1802'spermissions: {}addition is included.Testing
Ran
snapshot_docs.shend to end from this branch against a local bare remote with stubbedgh: it built the 0.9.0 snapshot, setlastVersionto 0.9.0, and opened the sync PR tomain. The snapshot matchesrelease/v0.9'sdocs/docsapart from the generated API and CLI pages. shellcheck and actionlint are clean, and zizmor reports the same findings asmain(5 lowself-repositorynotes, no ignores inzizmor.yml).Attribution
Adding a new component, requirement, sampling strategy, or tool?
If your PR adds or modifies one of the types below, check the matching box. A checklist of type-specific review items will be posted as a comment.