Skip to content

Commit 1a79d11

Browse files
TMHSDigitalclaude
andcommitted
ci: keep a failed Pages rebuild from blocking the release image
The Pages rebuild added in #385 runs in the release job after the release is public. publish-image needs that job, so a Pages failure would have skipped the GHCR image for an already published release. Make the step continue on error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 parent 54d48c5 commit 1a79d11

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

‎.github/workflows/go.yml‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -434,8 +434,11 @@ jobs:
434434
# workflow for an event caused by GITHUB_TOKEN, so a GoReleaser publish
435435
# never fires it (#370). Start the rebuild directly. It checks out main and
436436
# the header reads the latest release from the Pages metadata, so the site
437-
# shows the tag that was just published.
437+
# shows the tag that was just published. The release is already public
438+
# here and publish-image needs this job, so a failed rebuild is a warning,
439+
# not a failed release; rerun pages.yml by hand if it happens.
438440
- name: Rebuild GitHub Pages
441+
continue-on-error: true
439442
env:
440443
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
441444
shell: bash

0 commit comments

Comments
 (0)