ci(docs): stop archiving the docs version automatically on a release cut - #23571
Merged
Conversation
Reverts the `archive-previous-docs-version` job added in #22691. Cutting a release branch no longer opens a docs-archive PR by itself; the archive is done by dispatching `docs-version-bump.yml`, which #22066 added for exactly that and which stays as it is. Only the automation goes. `docs-version-bump.yml` is untouched, including the five-archive cap #22691 raised from three — that is a retention policy rather than part of the trigger, and lowering it again would prune v3.3 at the next bump. `notify` loses the job from `needs` along with the three outputs it consumed and the "Docs archive" embed field, so the Discord notification still reports the cut itself. Removed by hand rather than with `git revert`: #23284 and two action bumps have touched this file since, and reverting the commit would have taken those with it. zizmor reports no findings, unchanged from before (the three suppressions it counted inside the removed job go with it), and the workflow still parses with `create-release-branch` -> `notify` as the only edge.
lystopad
approved these changes
Aug 26, 2026
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
2 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.
Cutting a release branch used to open a docs-archive PR by itself. This removes that.
The snapshot goes stale almost immediately. Docs keep changing after a branch is cut, so a version archived at cut time stops matching the release it is meant to describe within days. Archiving is worth doing once the docs for a release have actually settled — that is a judgement call, not something to hang off the cut.
So the
archive-previous-docs-versionjob from #22691 is gone. Archiving stays a deliberate step: dispatchdocs-version-bump.yml(#22066), which is untouched and still does the whole thing in one click.notifyloses the archive field from its Discord embed but still reports the cut. The five-archive retention cap that #22691 also raised stays as it is — separate policy, and lowering it would prune v3.3 at the next bump.Removed by hand rather than with
git revert: #23284 and two action bumps have touched this file since, so reverting the commit would have taken those with it.zizmorreports no findings, unchanged from before, and the workflow still parses withcreate-release-branch→notifyas its only edge.