Changesets v3: Leaner Installs & Smarter Peer Bumps

Monorepo Management Reimagined

Changesets v3 represents a significant evolution for a critical tool in the monorepo ecosystem. The drastic reduction in install size (88%) and dependency count, coupled with the ESM-only shift, signals a commitment to modern JavaScript development practices and performance. The most impactful change is undoubtedly the adjustment in how peer dependencies are handled – bumping them by patch instead of major version. This directly addresses years of community frustration, acknowledging that not all peer dependency updates are breaking changes. This pragmatic approach, while potentially polarizing for those who prefer a stricter interpretation, aligns better with the reality of many development workflows and reduces unnecessary friction. The rebuilt CLI, leveraging cac and clack, promises a more robust and user-friendly interactive experience, fixing critical issues like crashing on cancelled prompts. The introduction of pack and publish-plan commands further streamlines the build and publish process, aligning with community best practices. The move to modern tooling like tsdown, rolldown, vitest, and oxfmt internally suggests a focus on developer experience and performance for the Changesets project itself, which often translates to better outcomes for its users.

However, the hardcoded nature of the peer dependency bumping (always patch, never major) does present a potential limitation. As noted by the Bumpy competitor, this might be an overcorrection, and the lack of configuration for propagation leaves users without the flexibility to define their own risk tolerance or project-specific semantic versioning interpretations. While the ability to add an explicit major changeset for genuine breaking changes exists, the default behavior could still lead to unintended consequences if not carefully managed. The absence of pnpm catalog support and the unchanged prerelease design, as mentioned, are also areas for potential future enhancement. For developers accustomed to the previous version or those with highly specific release strategies, the upgrade will require attention to configuration changes and potential adjustments to release playbooks, especially given the new exit code behavior for empty releases. Despite these points, the overall direction of v3 is overwhelmingly positive, focusing on efficiency and developer experience.

Key Points

• Changesets v3 is released after seven years, focusing on leaner installs and improved peer dependency handling.
• Install size reduced by 88% (16.1MB to 2.1MB), with dependencies cut from 95 to 39.
• All packages are now ESM-only, requiring Node.js 22.11+ and updated package managers.
• Peer dependency updates now default to a patch bump, addressing long-standing community complaints about unnecessary major version bumps.
• CLI rebuilt with cac and clack for better argument parsing and interactive prompts, fixing stability issues.
• New pack and publish-plan commands align with recommended build/publish sequences.
• Configuration changes include replacing Prettier with format detection and adjustments to private package versioning.
• changeset version now exits with code 1 for empty releases, impacting automated scripts.
• Continues to differentiate from semantic-release and release-it by requiring explicit contributor-written release intent.

---

📖 Source: Changesets v3: Bumps Peer Dependents by Patch and Ships ESM Only with an 88% Smaller Install