docs: snapshot v0.4.0 (manual fix for failed release-snapshot job)#287
Merged
docs: snapshot v0.4.0 (manual fix for failed release-snapshot job)#287
Conversation
The release workflow's snapshot-versioned-docs job ran on the v0.4.0
release but failed at the final `git push origin main` step because
main is now protected and rejects direct pushes (even from the
github-actions bot):
remote: error: GH006: Protected branch update failed for refs/heads/main.
remote: - Changes must be made through a pull request.
remote: - 7 of 7 required status checks are expected.
The snapshot itself was correctly generated by the workflow (per its
log), it just couldn't land it on main. Reproducing the same sed
transformations locally for docs/v/0.4.0/{index,guide,reference}/
and shipping via the proper develop → main path.
Changes:
- docs/v/0.4.0/index.html, guide/index.html, reference/index.html
(generated using the same sed transformations as release.yml — paths
rewritten to /git-parsec/v/0.4.0/, robots noindex, demo.gif src
absolute, data-doc-version="0.4.0")
- docs/versions.json: latest = "0.4.0", new entry prepended
- docs/sitemap.xml: 3 new /v/0.4.0/{,/guide/,/reference/} entries
Note: v0.4.0 binary (crates.io) and GitHub Release are already shipped
correctly. This PR only fills the missing versioned docs archive.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This was referenced May 4, 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
1 participant
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.
Why
The v0.4.0 release workflow's
snapshot-versioned-docsjob failed at the finalgit push origin mainstep:```
remote: error: GH006: Protected branch update failed for refs/heads/main.
remote: - Changes must be made through a pull request.
remote: - 7 of 7 required status checks are expected.
```
The snapshot files were generated correctly inside the workflow runner, just couldn't land on main due to the protected-branch rule. Other release jobs (Tag & Publish, 4-OS binary builds, GitHub Release) all succeeded — v0.4.0 is on crates.io and Releases is fine. Only the versioned docs archive at `/v/0.4.0/` is missing.
What
Reproduces the workflow's sed transformations locally and ships through the proper PR path.
Verified
Follow-up (separate)
Long-term, the release.yml's snapshot job needs to either (a) use a PAT/app token with bypass perms, or (b) push to a feature branch and open a PR instead of direct push, so this doesn't fail on every release going forward. Tracked separately.
🤖 Generated with Claude Code