Releases

Releases are cut by release-please from Conventional Commits on main: it opens a release PR that bumps the version (in .release-please-manifest.json and package.json) and writes the changelog, and merging it tags the release. Swift consumers pin those tags; the npm package will publish from them.

• Title PRs as Conventional Commits (feat:, fix:, docs:, …): the title is what release-please reads.
• Merge PRs with a merge commit so the branch's history is kept.
• Breaking changes to a token name, a Swift symbol or a CSS class are feat!: and need a major bump.

This site

The Cloudflare Worker signal serves docs/ as static assets (wrangler.jsonc, with docs/404.html for missing paths) at signal.chitransit.app, and deploys from main.