Affected Packages
Idk
Problem
I may not be ready for a release, but i may want folks to be able to test out changes without manually doing pre-reloason
Proposed solution
Provide an unstable option in config. When true, every merge is published (provided the changesets declare changes) with the git sha appended to the version. This uses the 'unstable' tag on npm, and does not create github releasen, nor remove the changeset files
Affected Packages
Idk
Problem
I may not be ready for a release, but i may want folks to be able to test out changes without manually doing pre-reloason
Proposed solution
Provide an unstable option in config. When true, every merge is published (provided the changesets declare changes) with the git sha appended to the version. This uses the 'unstable' tag on npm, and does not create github releasen, nor remove the changeset files