Release Policy

Publishing is changeset-driven from the monorepo root.

Authoritative flow

1. Make the package or docs change in shared-packages.
2. Add a Changeset if a published package contract changes.
3. Merge to main.
4. Let the versioning and publish workflows open or merge the release PR.
5. Consume the published package versions in downstream apps.

Release expectations

• yarn lint, yarn typecheck, yarn test, yarn build, and yarn validate:packages must all pass.
• Docs changes that affect package discovery should also run yarn docs:build and yarn docs:validate.
• Release notes come from Changesets; package changelogs remain the package-local audit trail when present.

Docs sync

The docs hub is rendered in douglasebanks.com, but the source of truth lives here. When repo docs or package contracts move, regenerate the docset manifest and sync it so the public docs stay aligned with the published workspace state.