Skip to content

ci: deploy Pages on tag push and bump Node 20 → 22#58

Merged
avanelsas merged 1 commit into
mainfrom
ci/tag-deploy-and-node-22
May 13, 2026
Merged

ci: deploy Pages on tag push and bump Node 20 → 22#58
avanelsas merged 1 commit into
mainfrom
ci/tag-deploy-and-node-22

Conversation

@avanelsas
Copy link
Copy Markdown
Owner

Summary

  • Pages deploys on tag push. The workflow only fired on release: published, so v0.4.0 / v0.5.0 / v0.6.0 tags left the hosted demo stuck on v0.3.0. Trigger is now push: tags: ['v*'] — a tag push is the single source of truth, and publishing a GitHub Release won't double-fire. workflow_dispatch is still available for manual asset-only refreshes.
  • Node 20 → 22 (current LTS). Updated in ci.yml, pages.yml, .tool-versions, and docs/dev-setup.md. Node 20 is being removed from GitHub-hosted runners on 2026-09-16.

Test plan

  • ./scripts/check.sh green locally (lint, fmt, tests, release build) on Node 22.
  • CI green on this PR (first run on Node 22).
  • After merge: next v* tag push triggers a Pages deploy automatically.

🤖 Generated with Claude Code

The Pages workflow only fired on `release: published`, so tags
v0.4.0 / v0.5.0 / v0.6.0 left the hosted demo stuck on v0.3.0.
Switching the trigger to `push: tags: ['v*']` makes a tag push
the single source of truth for a deploy — publishing a Release
isn't required and won't double-fire.

Also bumps Node 20 → 22 (current LTS) in ci.yml, pages.yml,
.tool-versions, and dev-setup.md. The Node 20 actions runtime
is being removed from GitHub-hosted runners on 2026-09-16.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@avanelsas avanelsas merged commit 8672201 into main May 13, 2026
1 check passed
@avanelsas avanelsas mentioned this pull request May 16, 2026
7 tasks
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