It would be cool to have an ability to release changes to some "beta stream" on npm for testing purposes.
Yarn link and portal protocols or resolutions are not always a solution. In my opinion better stand as closer to clients environment as we can, so that feature seem absolutely necessary. Especially for monorepos.
I see it next way in case of github repo:
user makes pull request with a couple commits
some "beta release" action calls
affected packages releases with versions like package1@14.0.1-beta.0package2@2.3.1-beta.0
Since zx-bulk-release always uses specific versions for packages deps, in won't be a problem to just bump last digit every time when another beta version already exists. Not too semantic, but I can't find better solution at this time 🙃
Actual behavior
[x] I've read the docs. This case is not mentioned
Issue type
Expected behavior
It would be cool to have an ability to release changes to some "beta stream" on npm for testing purposes. Yarn
linkandportalprotocols orresolutionsare not always a solution. In my opinion better stand as closer to clients environment as we can, so that feature seem absolutely necessary. Especially for monorepos.I see it next way in case of github repo:
package1@14.0.1-beta.0package2@2.3.1-beta.0Since zx-bulk-release always uses specific versions for packages deps, in won't be a problem to just bump last digit every time when another beta version already exists. Not too semantic, but I can't find better solution at this time 🙃
Actual behavior