Versionado y publicación de paquetes compartidos de tRPC

In a monorepo, many apps depend on shared packages such as your tRPC router types. Without disciplined versioning, a breaking change in one package silently breaks every consumer.

Apps reference internal packages using the workspace protocol, so they always use the local source.

Follow semver for shared packages:

• patch — bug fixes
• minor — backward-compatible features
• major — breaking API changes

A changed tRPC input schema is often a breaking change.

The changesets tool tracks intended version bumps. Each change records which packages changed and at what level.

A changeset is a small markdown file describing the bump and a summary that becomes a changelog entry.

Run the version command to consume all pending changesets, bump package.json files, and update changelogs.

If you publish to a registry, the publish command pushes only the packages that changed.

Many monorepos never publish to npm. Mark shared packages as private so they are versioned for clarity but never accidentally published.

When a tRPC router changes shape, a major bump signals consumers to update. Because types flow through the monorepo, TypeScript will flag every broken call site at build time.

A common workflow opens a release pull request automatically whenever changesets are merged, so versioning never depends on someone remembering to run it.

Keep releases sane:

• Require a changeset in every feature PR
• Treat schema changes as breaking
• Keep changelogs human-readable
• Let CI own the version bump

You learned to version shared tRPC packages:

• Use the workspace protocol for internal deps
• Follow semver; schema changes are breaking
• Track bumps with changesets
• Automate releases in CI

Your monorepo now evolves safely across many consumers.