-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should not list private packages in version PR #214
Comments
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? |
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. |
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 |
The One way is to skip private packages without a Currently, there is another bug that requires private package to have a version field, or else the publish fails. |
FYI, here is a problem with the |
And the private package
workspace:*
don't need to get updated.e.g.:
![image](https://user-images.githubusercontent.com/3254987/189462867-a473960d-cc0e-4d2a-9f4b-8e38cc7d62b0.png)
clibuilder/clibuilder#407
The text was updated successfully, but these errors were encountered: