Upgrade deployment workflow to GitHub native actions

[Copilot]

Upgrades the release.yml deployment workflow from the third-party peaceiris/actions-gh-pages@v3 to GitHub's native first-party Pages deployment actions.

Changes Made

• Replaced peaceiris/actions-gh-pages@v3 with two GitHub-native steps:
  • actions/upload-pages-artifact@v3 — packages the Docusaurus build output as a GitHub Pages artifact
  • actions/deploy-pages@v4 — deploys the uploaded artifact to GitHub Pages
• Updated permissions:
  • Removed contents: write (no longer needed; the native flow doesn't push to a gh-pages branch)
  • Changed contents to read
  • Added pages: write (required for Pages deployment)
  • Added deployments: write (required by actions/deploy-pages)
• Added environment configuration on the job (name: github-pages, url: ${{ steps.deployment.outputs.page_url }}), enabling GitHub Pages environment protection rules and deployment status tracking in the GitHub UI
• Added concurrency group (group: pages, cancel-in-progress: false) at the workflow level to prevent concurrent manual release runs from overwriting each other's deployment status or environment URL

Why

• Eliminates third-party dependency in the deployment pipeline
• Uses GitHub's officially supported Pages deployment flow
• Better integration with GitHub Pages environments and deployment protection rules
• Concurrent deployments are safely queued rather than cancelled
• No functional change to the site itself

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Upgrade deployment workflow from peaceiris/actions-gh-pages@v3 to GitHub native actions/deploy-pages</issue_title>
<issue_description>The release.yml workflow uses peaceiris/actions-gh-pages@v3 for GitHub Pages deployment. This is a third-party action that is now outdated (v4 exists), and GitHub provides native first-party actions for Pages deployment (actions/upload-pages-artifact + actions/deploy-pages).

Current: peaceiris/actions-gh-pages@v3
Proposed: actions/upload-pages-artifact@v4 + actions/deploy-pages@v4

Why:

• Eliminates third-party dependency in the deployment pipeline
• Uses GitHub's officially supported Pages deployment flow
• Better integration with GitHub Pages environments and deployment protection rules
• No functional change to the site itself</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Upgrade deployment workflow from peaceiris/actions-gh-pages@v3 to GitHub native actions/deploy-pages #765

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[hemarina]

@copilot Continue running original prompt

[Copilot]

@copilot Continue running original prompt

Done! Implemented the upgrade in commit c72d92b. Here's a summary of what changed in release.yml:

• Replaced peaceiris/actions-gh-pages@v3 with two GitHub-native steps:
  • actions/upload-pages-artifact@v3 — uploads the built site as a Pages artifact
  • actions/deploy-pages@v4 — deploys the artifact to GitHub Pages
• Updated permissions: removed contents: write (no longer needed), added pages: write and deployments: write
• Added environment block with name: github-pages and the deployment URL output, enabling GitHub Pages environment protection rules and deployment tracking

[Copilot]

Pull request overview

Updates the manual release.yml workflow to deploy the Docusaurus site to GitHub Pages using GitHub’s first-party Pages deployment actions instead of a third-party gh-pages publisher action.

Changes:

• Replaces peaceiris/actions-gh-pages@v3 with actions/upload-pages-artifact@v3 + actions/deploy-pages@v4.
• Adjusts workflow permissions for the GitHub Pages OIDC-based deployment flow.
• Adds a github-pages environment with the deployed page_url for environment tracking/protection.

---

You can also share your feedback on Copilot code review. Take the survey.