Skip to content

ci: deploy Pages only for releases, with the version from the tag - #7

Merged
MathiasVDA merged 1 commit into
mainfrom
ci/pages-no-release-trigger
Oct 21, 2026
Merged

MathiasVDA merged 1 commit into
mainfrom
ci/pages-no-release-trigger

Conversation

@MathiasVDA

@MathiasVDA MathiasVDA commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Requested by Mathias · project thread

The site should always match a released version, and the version should come from the release tag rather than be hardcoded on main.

  • Pages no longer deploys on pushes to main; it deploys when a release is published, or by manual dispatch (optional tag input, defaulting to the latest release).
  • The build checks out the release tag and runs scripts/set-version.sh with the tag's version before building, the same way release.yml does.

Needed in the repo settings: the github-pages environment currently only allows main, which is why the v1.0.0 deploy was rejected. Add a deployment tag rule v* under Settings → Environments → github-pages.

https://claude.ai/code/session_01FCUYsYqK19KAw1CwEpoiXe


Generated by Claude Code

@MathiasVDA MathiasVDA self-assigned this Oct 21, 2026
@MathiasVDA MathiasVDA changed the title ci: deploy Pages only from main, not on releases ci: deploy Pages only from main and set the version to 1.0.0 Oct 21, 2026
@MathiasVDA MathiasVDA changed the title ci: deploy Pages only from main and set the version to 1.0.0 ci: deploy Pages only for releases, with the version from the tag Oct 21, 2026
@MathiasVDA
MathiasVDA force-pushed the ci/pages-no-release-trigger branch from eaa5113 to 902aa78 Compare October 21, 2026 21:10
@MathiasVDA
MathiasVDA merged commit 5c75db7 into main Oct 21, 2026
6 checks passed
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.

1 participant