ci: migrate GitHub Pages to Actions-based deployment#64
Merged
Conversation
The legacy 'deploy from a branch' Pages build (gh-pages) began failing with '401 Requires authentication' from the auto-injected pages-build-deployment workflow. Add a deploy-pages job to the release workflow that publishes the gh-pages content via actions/upload-pages-artifact + actions/deploy-pages, and flips the Pages build type from legacy to workflow via configure-pages enablement on first run.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
GitHub Pages for
helm.truvami.comstarted failing on 2026-06-10 with:The error comes from GitHub's auto-injected
pages-build-deploymentworkflow that runs on everygh-pagespush (legacy "deploy from a branch" mode). All config was verified healthy (Pages enabled, valid cert,gh-pagesallowed by thegithub-pagesenvironment branch policy,writedefault token perms). It worked on 2026-06-09 and broke on 2026-06-10 with no config change — the legacy deploy pipeline appears to be in a wedged state (the latest legacy build is stuck inbuilding).Fix
Migrate Pages publishing from the legacy branch build to the GitHub Actions deployment pipeline. A new
deploy-pagesjob inrelease.yml:charts(so it deploys the freshly-updatedindex.yaml)gh-pages, stages it into_site(excluding.git)actions/configure-pages@v5withenablement: true— flips the Pages build typelegacy→workflowon first runactions/upload-pages-artifact@v3+actions/deploy-pages@v4The custom domain (
helm.truvami.com) and cert are stored at the repo level and persist across the build-type change;CNAMEis also retained in the uploaded artifact.After merge
pages-build-deploymentworkflow stops auto-running once the build type isworkflow.configure-pagesenablement does not auto-flip the existing legacy site, set Settings → Pages → Source → GitHub Actions once, then re-run the workflow.