JORVEL

Changelog

JORVEL uses Changesets. Every change adds a changeset; the release workflow (.github/workflows/release.yml, scaffolded at init) opens a version PR and, on merge, bumps versions + publishes + writes per-package CHANGELOG.md.

The flow

bash
pnpm changeset            # describe the change + pick bump (patch/minor/major)
pnpm version              # apply bumps + regenerate CHANGELOG.md (usually done by CI)
pnpm release              # publish to npm (CI, on merge to main)

Where to read it

Semver + contracts

Breaking federation-contract changes surface in CI via jorvel federation diff before they merge — so a major bump is a deliberate, visible act, not a surprise.