Skip to content

ci: 🚀 deploy the website after each release, from GitHub Actions - #74

Merged
diecodev merged 1 commit into
mainfrom
ci/website-deploy
Oct 29, 2026
Merged

diecodev merged 1 commit into
mainfrom
ci/website-deploy

Conversation

@diecodev

Copy link
Copy Markdown
Owner

Vercel built the website on every push, a library change or a release
commit too, and before the new version was on npm. The website now
deploys from GitHub Actions (website.yml, with the Vercel CLI: the build
runs with the CI's pnpm and Node, and Vercel serves it), only:

  • after each release, once the version is public on npm: release.yml
    waits for the approval (npm stage approve, up to 6 hours), publishes
    the GitHub release that was a draft, and calls it;
  • on a push to main that changes website/ or vercel.json;
  • by hand.

Vercel builds nothing from Git for main any more. A branch that changes
website/ or vercel.json, compared with main, still gets a preview from
its Git integration (website/scripts/vercel-preview.sh, its Ignored
Build Step); the rest are skipped. The deploy needs VERCEL_TOKEN,
VERCEL_ORG_ID and VERCEL_PROJECT_ID as secrets, .vercel is ignored,
and CONTRIBUTING and the website's README describe the flow.


Stack created with GitHub Stacks CLI • Give Feedback 💬

Vercel built the website on every push, a library change or a release
commit too, and before the new version was on npm. The website now
deploys from GitHub Actions (website.yml, with the Vercel CLI: the build
runs with the CI's pnpm and Node, and Vercel serves it), only:

- after each release, once the version is public on npm: release.yml
  waits for the approval (`npm stage approve`, up to 6 hours), publishes
  the GitHub release that was a draft, and calls it;
- on a push to main that changes website/ or vercel.json;
- by hand.

Vercel builds nothing from Git for main any more. A branch that changes
website/ or vercel.json, compared with main, still gets a preview from
its Git integration (website/scripts/vercel-preview.sh, its Ignored
Build Step); the rest are skipped. The deploy needs VERCEL_TOKEN,
VERCEL_ORG_ID and VERCEL_PROJECT_ID as secrets, `.vercel` is ignored,
and CONTRIBUTING and the website's README describe the flow.
@vercel

vercel Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
qwik-date Ready Ready Preview Oct 29, 2026 5:16pm UTC

@diecodev
diecodev added this pull request to stack #77 October 29, 2026 17:15
@diecodev
diecodev merged commit 6eae9d2 into main Oct 29, 2026
5 checks passed
@diecodev
diecodev deleted the ci/website-deploy branch October 29, 2026 18:21
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