Skip to content

fix(ci): rebuild GitHub Pages after a release is published - #385

Merged
TMHSDigital merged 2 commits into
TMHSDigital:mainfrom
SatriaBagusNurhadianto:fix/pages-rebuild-after-release
Nov 16, 2026
Merged

TMHSDigital merged 2 commits into
TMHSDigital:mainfrom
SatriaBagusNurhadianto:fix/pages-rebuild-after-release

Conversation

@SatriaBagusNurhadianto

Copy link
Copy Markdown
Contributor

What changed:

  • go.yml now starts the GitHub Pages workflow directly after the release is published, and waits for it, because the release: published trigger never fires for a release published with GITHUB_TOKEN.
  • The release job gets actions: write, which gh workflow run and gh run watch need.
  • pages.yml documents that its release trigger only covers a release published outside the release workflow.

Why:

Tests:

  • actionlint .github/workflows/*.yml passes (actionlint 1.7.12).
  • Both workflows parse as YAML, and gh run list --json databaseId,createdAt confirms the fields the new step uses.
  • No Go code changed, so go test ./... was not run. The change is CI-only.

Related: #370

@TMHSDigital
TMHSDigital merged commit 272f954 into TMHSDigital:main Nov 16, 2026
17 checks passed
TMHSDigital added a commit that referenced this pull request Nov 16, 2026
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pages never rebuilds on a release published with GITHUB_TOKEN

2 participants