From b83d3b315909dd7a246a3248f2f718fa3593f373 Mon Sep 17 00:00:00 2001 From: phantomptr Date: Sun, 11 Oct 2026 00:22:06 -0700 Subject: [PATCH] Pages: drop the release trigger, which the environment always rejected A release event runs on the tag's ref, and the github-pages environment only deploys from main: every release showed a failed deploy ('Tag v7.0.6 is not allowed to deploy to github-pages'). The deploy after publish (from main) already covers new releases, and the daily run picks up a hand-promoted one; the page reads releases live anyway. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01Ub1mez9eaVtTF8pMEFXvA9 --- .github/workflows/pages.yml | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/.github/workflows/pages.yml b/.github/workflows/pages.yml index 8c8d6930..48c65ce5 100644 --- a/.github/workflows/pages.yml +++ b/.github/workflows/pages.yml @@ -8,10 +8,9 @@ name: pages # # When it deploys: # - a change to site/ (or this file) on main; -# - after the publish workflow finishes. A release made by publish.yml does not fire the -# `release` event below: GitHub doesn't start workflows from its own token's actions; -# - a release published, edited or deleted by hand (promoting a pre-release is an edit); -# - once a day, so the snapshot never drifts far; +# - after the publish workflow finishes; +# - once a day, so the snapshot never drifts far (this is what picks up a pre-release promoted +# by hand; the page itself reads the releases API live, so visitors see it at once); # - by hand (Actions → pages → Run workflow). on: @@ -21,8 +20,8 @@ on: workflow_run: workflows: [publish] types: [completed] - release: - types: [published, edited, deleted] + # No `release` trigger: that run's ref is the tag, and the github-pages environment only + # deploys from main, so it was always rejected ("Tag ... is not allowed to deploy"). schedule: - cron: "17 6 * * *" workflow_dispatch: