Publish pre-release while change-set pull-request is open

[smeijer]

I'd like to publish my packages, before the final publish step, while the changeset pull-request is still open. The workflow is currently:

1. author merges a pull request having a changeset
2. changeset opens pull-request to version & release packages
3. author merges changeset pull-request
4. changeset publishes stable version (major.minor.patch)

What I like to see different, is that while the changeset pull-request is open (2), every change to a package get's published as pre-release. That way, we can test packages from npm, before merging the pull-request (3) and publishing a new stable version.

I know we already can publish pre-releases using changeset, but to my understanding that'd still lead to the same workflow as above, meaning all those pre-releases also require new changeset pull-requests. I'd like to keep the pull-request open while publishing pre-releases and polishing the package for final release.

[ben-laird]

+1 to the above, sorry I can't help at all with the issue!

[TheSonOfThomp]

Would love to see this as well.

You wouldn't necessarily need to publish a new pre-release for every package on each merge, only if there are new changes.

[marklundin]

@smeijer Did you find a solution to this?

[smeijer]

@marklundin , i'm currently running pkg.pr.new on the changeset pull/branch instead. It doesn't give you canaries on npm, but it works reasonably well.