From e64bdacb3b7a499524f5b988cec33465ae80d4fa Mon Sep 17 00:00:00 2001 From: sn0wm1ku Date: Thu, 9 Jul 2026 21:00:51 +0900 Subject: [PATCH 1/2] Fix Pages deploy: trigger release on push to release branch The Release workflow triggered on `pull_request: closed [release]`, so its jobs ran in the PR-merge ref context (refs/pull/N/merge). The github-pages environment only allows deployments from the `main`/`release` branches, so the deploy was always rejected ("Branch refs/pull/N/merge is not allowed to deploy to github-pages"). The workflow had in fact never deployed successfully. Follow the official VitePress GitHub Pages guide: trigger on `push` to the release branch (plus workflow_dispatch). The run then executes in the `release` branch context, which is now an allowed deployment branch for the github-pages environment, so deploy-pages succeeds. Also drop the `if: github.event.pull_request.merged == true` guards on all three jobs (obsolete once the trigger is push/dispatch rather than pull_request). Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/release.yml | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 1ffdde9..e419ba2 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -1,7 +1,6 @@ name: Release on: - pull_request: - types: [closed] + push: branches: - release @@ -26,8 +25,6 @@ concurrency: jobs: build: name: Build VitePress - # 'merged == true' to prevent from being triggered when PR is closed - if: github.event.pull_request.merged == true runs-on: ubuntu-latest steps: - name: Checkout @@ -54,7 +51,6 @@ jobs: deploy: name: Deploy to GitHub Pages - if: github.event.pull_request.merged == true environment: name: github-pages url: ${{ steps.deployment.outputs.page_url }} @@ -67,7 +63,6 @@ jobs: publish-release-note: name: Publish release note - if: github.event.pull_request.merged == true needs: deploy permissions: contents: write From 552efc1f1e95da2ddfb9a000ad82b0d57322fe10 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Thu, 9 Jul 2026 12:02:26 +0000 Subject: [PATCH 2/2] Initial commit for the issue #76