Should not list private packages in version PR

[unional]

And the private package workspace:* don't need to get updated.

e.g.:
clibuilder/clibuilder#407

[smeijer]

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]

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]

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 ignore option?

[unional]

The ignore option 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 version field.

Currently, there is another bug that requires private package to have a version field, or else the publish fails.

[unional]

FYI, here is a problem with the ignore option: changesets/changesets#1093

[bluwy]

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.