Revert Pages actions v4->v5 in release.yml to fix broken prod deploy - #883
Merged
Conversation
actions/upload-pages-artifact@v5 internally upgraded to upload-artifact@v7, which produces artifacts in a format that actions/deploy-pages@v5 cannot consume. Both steps report success but the published artifact is empty, so GitHub Pages falls back to serving the gh-pages branch via Jekyll, rendering README.md instead of the Docusaurus gallery. Revert both to v4 (still SHA-pinned) until deploy-pages ships an aligned release. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Marina He (hemarina)
had a problem deploying
to
github-pages
May 20, 2026 17:09 — with 
GitHub Actions
Failure
GitHub Actions
Failure
Contributor
There was a problem hiding this comment.
Pull request overview
This PR aims to restore the GitHub Pages production deployment for the Docusaurus-based Awesome AZD site by reverting the Pages Actions from v5 back to v4 in the release workflow, aligning the upload and deploy steps to a compatible artifact format.
Changes:
- Revert
actions/upload-pages-artifactfrom v5.0.0 to v4.0.0 (pinned by SHA). - Revert
actions/deploy-pagesfrom v5.0.0 to v4.0.5 (pinned by SHA).
Marina He (hemarina)
enabled auto-merge (squash)
May 20, 2026 17:15
JeffreyCA
approved these changes
May 20, 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.
Summary
Revert
actions/upload-pages-artifactandactions/deploy-pagesfrom v5 back to v4 inrelease.yml.Why
The v4 → v5 bump introduced in #876 broke the production deploy. After PR #876 merged, the live site at https://azure.github.io/awesome-azd/ began serving the raw
README.md(Jekyll-rendered) instead of the Docusaurus gallery, even though theRelease Awesome Azdworkflow continues to report green.Root cause:
actions/upload-pages-artifact@v5updated its internal dependency toactions/upload-artifact@v7(per its release notes: "Update upload-artifact action to version 7").upload-artifact@v7produces artifacts using the new immutable-artifacts API.actions/deploy-pages@v5was not updated to consume that new format — its release notes are limited to a Node.js 24 bump and small chores.sync-gh-pages.ymlforce-pushes togh-pages— which Jekyll renders asREADME.md.Change
Both pinned by SHA. Other action bumps from #876 (checkout v6.0.2, setup-node v6.4.0) are kept.
Validation
Release Awesome Azdongh-pagesand verify https://azure.github.io/awesome-azd/ renders the gallery (not the README).actions/deploy-pagesships a release that aligns withupload-artifact@v7.