Release tooling

Release tooling interviews judge compatibility communication: semver semantics, human-readable changelogs, multi-package versioning, and traceability from tag to reviewed changes. Subtopics: semantic versioning, Changesets, conventional commits.

On interviews: classify a behavior change as major/minor/patch; describe how Changesets or conventional commits feed automation without replacing review.

Common pitfalls: semver labels that hide breaking API changes; squash workflows losing release messages; forgetting changesets in multi-package PRs.

The trade-off is automation speed versus consumer trust in version meaning.

Checklist:

• Define public API boundaries.
• Mark breaking changes explicitly.
• Keep changelog text consumer-readable.
• Align squash/merge with release automation.