saberland/saber
Do you want to work on this issue?
You can request for a bounty in order to promote it!
Automatically publish a release per commit #86
egoist posted onGitHub
When there's a bug fix or new feature landed in master we should automatically publish the package as saber-next
on npm, so that you can try out the new version without waiting us to actually update saber
on npm.
The question is: should we use a new format of package name, e.g. saber-next
or saber@next
channel instead?