Skip to content

[FR] Add --include parameter as a counterpart to --ignore #1672

Description

@DaveFz

Description

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).

Activity

  1. ashnaarya commented on Jun 23, 2026

    @ashnaarya

    Are there any updates here? Would also love an --include config option as we only plan to version 1-2 packages

  2. Andarist commented on Jun 24, 2026

    @Andarist
    Member

    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 😉

  3. Boulea7 commented on Aug 13, 2026

    @Boulea7

    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.

  4. beeequeue commented on Aug 13, 2026

    @beeequeue
    Member

    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).

  5. Andarist commented on Aug 13, 2026

    @Andarist
    Member

    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.

  6. AlvaroGraca-TomTom commented on Oct 2, 2026

    @AlvaroGraca-TomTom

    Any update on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions