Repository navigation
ci: revert upload-pages-artifact to v3.0.1 (Pages deploy hang A/B test) - #279
Merged
Merged
Conversation
ben-harris-5
approved these changes
Nov 10, 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
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
After #278 (bump
upload-pages-artifactto v4.0.0), the Pages deploy hangs:deploy-pagespolls "Getting Pages deployment status" with an empty status for 10 minutes, then times out and cancels. This happened twice onde8c0dc:The build and artifact upload succeed (157 MB, same size as before), and githubstatus shows Pages/Actions operational. Every successful deploy used the v3 artifact; both hung deploys used the v4.0.0 artifact. This PR is an A/B test to see whether the artifact version is the cause.
Change
Revert only
actions/upload-pages-artifactto the previously used v3.0.1 (56afc60…), keeping the SHA pin and version comment.devvit-docsis now exempt from the "require full SHA" setting, and v3 only calls GitHub-ownedactions/upload-artifact@v4, which is allowed.What to check after merge
The "Deploy to GitHub Pages" run on
mainshould finish in roughly 3-4 minutes (previous successes: 184-480s).fc324d3…) or investigate the artifact.timeoutondeploy-pages.Notes
main, so it cannot be verified on the PR itself.