Deploy the site from a release branch moved on each published release (#207)

Co-authored-by: boratatouille <178141691+boratatouille@users.noreply.github.com>
This commit is contained in:
Grug
2026-10-23 09:09:26 +08:00
committed by GitHub
co-authored by boratatouille
parent 0b28009e38
commit 2a2c64c651
2 changed files with 45 additions and 0 deletions
+12
View File
@@ -28,3 +28,15 @@ Workers Builds settings:
- Enable builds for non-production branches for branch preview URLs.
Thanks for helping!
## Releases and the docs site
The site at basecoatui.com deploys from the `release` branch, not `main`, so the docs always match the version on npm. Nobody commits to `release` directly.
To release:
1. Bump the version in `package.json`, commit, tag (for example `1.1.0`) and push.
2. Run `npm publish`.
3. Publish a GitHub release for the tag, for example `gh release create 1.1.0 --generate-notes`.
Publishing the release runs `.github/workflows/deploy-site.yml`, which points `release` at the tag. Cloudflare then builds and deploys the site. To redeploy or roll back, run that workflow manually with the tag you want live.