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
Should not list private packages in version PR #214
I think it should? I'm using changesets in a private workspace with exclusively private packages and apps, just for the sake of tracking changes in the pull request, and releases page.
Why are you using changeset for those private packages if you don't want it to show the changes or bump the version?
In my case, there definitely is. I'm tracking my apps and apis. The source is not published to anyone, but the changes are tracked for customers, and communicated via a changelog and newsletter.
I don't track them all, so I never commit a changeset for say a project config, or tests.
If you don't want to version private packages, set privatePackages.version: false (true by default, but will be false by default in Changesets v3). When private packages are versioned, they should appear in the version PR.
Activity
smeijer commentedon Apr 21, 2023
I think it should? I'm using changesets in a private workspace with exclusively private packages and apps, just for the sake of tracking changes in the pull request, and releases page.
Why are you using changeset for those private packages if you don't want it to show the changes or bump the version?
unional commentedon Apr 21, 2023
Private packages are private. They are not published nor tracked. e.g. project configs, test packages, examples, github docs.
Their changes are tracked by source control commits. There is no need to track for versions.
There is no audience for those versions.
smeijer commentedon Apr 22, 2023
In my case, there definitely is. I'm tracking my apps and apis. The source is not published to anyone, but the changes are tracked for customers, and communicated via a changelog and newsletter.
I don't track them all, so I never commit a changeset for say a project config, or tests.
Are you perhaps looking for the
ignoreoption?unional commentedon Apr 22, 2023
The
ignoreoption supposed to be a temp solution.I can see your needs, so the question is how to handle both cases.
One way is to skip private packages without a
versionfield.Currently, there is another bug that requires private package to have a version field, or else the publish fails.
unional commentedon Apr 29, 2023
FYI, here is a problem with the
ignoreoption: changesets/changesets#1093bluwy commentedon Jul 28, 2026
If you don't want to version private packages, set
privatePackages.version: false(true by default, but will be false by default in Changesets v3). When private packages are versioned, they should appear in the version PR.