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
What is the improvement or update you wish to see?
The recommended package publishing workflow has a bad result. With the default changeset configuration, the script will bump package's versions, not commit or push the changes, and publish to npm at the uncommitted version. The result is the registry version bumps but the newly cut version has the unchanged package.json>"version" value.
Is there any context that might help us understand?
This field probably shouldn't be required.
Does the docs page already exist? Please link to it.
What is the improvement or update you wish to see?
The recommended package publishing workflow has a bad result. With the default changeset configuration, the script will bump package's versions, not commit or push the changes, and publish to npm at the uncommitted version. The result is the registry version bumps but the newly cut version has the unchanged package.json>"version" value.
Is there any context that might help us understand?
This field probably shouldn't be required.
Does the docs page already exist? Please link to it.
https://turbo.build/repo/docs/guides/publishing-libraries#using-changesets-with-turborepo
The text was updated successfully, but these errors were encountered: