You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FR] Add --include parameter as a counterpart to --ignore #1672
I would like to request the addition of an --include parameter to the changeset version command. This parameter would serve as a counterpart to the existing --ignore parameter.
Current Problem
The --ignore parameter requires specifying all packages except the one you want to release. This can be cumbersome, especially when you only want to release a single package.
Usage Example
changeset version --include <package-name>
This command would only version the specified package(s).
Reacted by Ben Limmer, Katie Redderson-Lear and Alvaro Graca
I can work on this. Should --include use the current --ignore semantics for every package outside the list? That would keep the existing guard against changesets that mix included and excluded packages, and leave dependency, fixed, and linked-group validation unchanged. Supporting partial application of one mixed changeset would need different handling so its remaining release entries stay pending.
A proper implementation would most likely also include a config file option as well as cli flag, to match the ignore capabilities.
The handling of ignore in the project right now is imo quite as subpar, with it being quite easy to miss integrating it in every place it should be (as can be seen with the bug with pre-releases).
Should --include use the current --ignore semantics for every package outside the list? That would keep the existing guard against changesets that mix included and excluded packages, and leave dependency, fixed, and linked-group validation unchanged.
Generally yes. If there are already scheduled releases for some packages, releasing only a subset from those... is dangerous. We shouldn't allow doing that by default.
Activity
ashnaarya commentedon Jun 23, 2026
Are there any updates here? Would also love an --include config option as we only plan to version 1-2 packages
Andarist commentedon Jun 24, 2026
It sounds like a reasonable request given we auto-derive managed packages from the workspaces configuration and there is no real way to override this.
PRs are welcome 😉
Boulea7 commentedon Aug 13, 2026
I can work on this. Should
--includeuse the current--ignoresemantics for every package outside the list? That would keep the existing guard against changesets that mix included and excluded packages, and leave dependency, fixed, and linked-group validation unchanged. Supporting partial application of one mixed changeset would need different handling so its remaining release entries stay pending.beeequeue commentedon Aug 13, 2026
A proper implementation would most likely also include a config file option as well as cli flag, to match the
ignorecapabilities.The handling of
ignorein the project right now is imo quite as subpar, with it being quite easy to miss integrating it in every place it should be (as can be seen with the bug with pre-releases).Andarist commentedon Aug 13, 2026
Generally yes. If there are already scheduled releases for some packages, releasing only a subset from those... is dangerous. We shouldn't allow doing that by default.
AlvaroGraca-TomTom commentedon Oct 2, 2026
Any update on this?