Minor Changes
-
#1840
057cca2Thanks @wotan-allfather! - Add--sinceflag toaddcommand
A tool to manage versioning and changelogs with a focus on monorepos
3 Mar 2026 · Newest first
Last checked
Checking sources…
Showing 1 of 1 releases. Full release notes.
#1840 057cca2 Thanks @wotan-allfather! - Add --since flag to add command
Signals highlight changes worth reviewing. They cannot determine whether your application is affected.
The add command now supports a --since flag that allows you to specify which branch, tag, or git ref to use when detecting changed packages. This is useful for gitflow workflows where you have multiple target branches and the baseBranch config option doesn't cover all use cases.
Example: changeset add --since=develop
If not provided, the command falls back to the baseBranch value in your .changeset/config.json.
#1845 2b4a66a Thanks @Andarist! - Delegate OTP prompting to the package manager instead of handling it in-process. This allows Changesets to use the package manager's native web auth support.
#1774 667fe5a Thanks @bluwy! - Support importing custom commit option ES module. Previously, it used require() which only worked for CJS modules, however now it uses import() which supports both CJS and ES modules.
#1839 73b1809 Thanks @leochiu-a! - Add a --message (-m) flag to changeset add (and default changeset) so the changeset summary can be provided from the command line. When --message is present, the summary prompt is skipped while the final confirmation step is kept.
#1806 0e8e01e Thanks @luisadame! - Changeset CLI can now be run from the nested directories in the project, where the .changeset directory has to be found in one of the parent directories
#1849 9dc3230 Thanks @Andarist! - Compute the terminal's size lazily to avoid spurious stderr output in non-interactive mode
#1857 2a73025 Thanks @mixelburg! - Fix confusing prompt labels when entering changeset summary after external editor fallback
#1842 6df3a5e Thanks @RodrigoHamuy! - Allow private packages to depend on skipped packages without requiring them to also be skipped. Private packages are not published to npm, so it is safe for them to have dependencies on ignored or unversioned packages.
#1776 503fcaa Thanks @bluwy! - Support absolute paths in changeset status --output <path>
Updated dependencies [667fe5a, 1772598, b6f4c74, 6df3a5e, 6df3a5e, 27fd8f4]: