Skip to content

Release Candidate 2026-07-09 21:19:40 +0900 - #79

Merged
sn0wm1ku merged 4 commits into
releasefrom
main
Jul 10, 2026
Merged

Release Candidate 2026-07-09 21:19:40 +0900#79
sn0wm1ku merged 4 commits into
releasefrom
main

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown

sn0wm1ku and others added 4 commits July 9, 2026 21:00
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) <noreply@anthropic.com>
Fix GitHub Pages deploy: Release workflow never deploys
@github-actions github-actions Bot changed the title Preparing release pull request... Release Candidate 2026-07-09 21:19:40 +0900 Jul 9, 2026
@github-actions github-actions Bot added the release-candidate Would only be set to a pull request from main to release. label Jul 9, 2026
@sn0wm1ku
sn0wm1ku merged commit 6b298c7 into release Jul 10, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-candidate Would only be set to a pull request from main to release.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants