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
I have three packages in a monorepo, and only one of them is actually publishable (the others have private: true.) When I run yarn changeset, it asks me which ones I want to write changesets for, including private packages. I very rarely change these other packages and dislike that the CLI forces me to choose which package to bump every time when the others are never relevant.
Proposed solution
Allow config to focus the CLI, specifically changeset add to a specific package or list of packages, or
Add a flag to changeset add to omit unpublishable packages
The text was updated successfully, but these errors were encountered:
quantizor
changed the title
[Bug] Ignored packages shown in CLI when writing a changeset
[Request] Filter packages shown in CLI when writing a changeset
Mar 12, 2024
Digging into the code, I noticed that there is an explicit check to ensure that version is not set for packages marked as private: true, why is that? Would it be OK if I removed that limitation?
That's actually reading out of the config. So if you set "privatePackages": false in your config.json, it will ignore private packages (whether they have a version or not).
Affected Packages
@changesets/cli
Problem
I have three packages in a monorepo, and only one of them is actually publishable (the others have
private: true
.) When I runyarn changeset
, it asks me which ones I want to write changesets for, including private packages. I very rarely change these other packages and dislike that the CLI forces me to choose which package to bump every time when the others are never relevant.Proposed solution
changeset add
to a specific package or list of packages, orchangeset add
to omit unpublishable packagesThe text was updated successfully, but these errors were encountered: