Skip to content

ci(release): auto-enable GitHub Pages in deploy step#175

Merged
pofallon merged 1 commit into
mainfrom
chore/pages-enablement
Jun 2, 2026
Merged

ci(release): auto-enable GitHub Pages in deploy step#175
pofallon merged 1 commit into
mainfrom
chore/pages-enablement

Conversation

@pofallon
Copy link
Copy Markdown
Contributor

@pofallon pofallon commented Jun 2, 2026

Summary

The v0.2.0-rc.1 release run failed only in the Deploy Install Script to GitHub Pages job:

Get Pages site failed. Please verify that the repository has Pages enabled and configured to build using GitHub Actions, or consider exploring the enablement parameter for this action.

GitHub Pages has never been enabled on this repo. This sets enablement: true on actions/configure-pages@v4, which creates the Pages site automatically using the job's existing pages: write permission — no manual repo settings required. Fixes the Pages job for the eventual v0.2.0 GA release.

Note: this does not retroactively fix the v0.2.0-rc.1 run (re-running a job uses the workflow at the tagged commit). All other rc.1 jobs — the 8-platform binaries, checksums, and SLSA provenance — succeeded and are published on the prerelease.

🤖 Generated with Claude Code

Set enablement: true on actions/configure-pages so the Pages site is
created automatically (using the job's pages: write permission) instead
of failing with 'Get Pages site failed' when Pages was never enabled.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added the ci CI/CD changes label Jun 2, 2026
@pofallon pofallon merged commit fc2b995 into main Jun 2, 2026
11 checks passed
@pofallon pofallon deleted the chore/pages-enablement branch June 2, 2026 01:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci CI/CD changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant