Stream: javascript
Topic: publishing
Cole Diffin (Apr 05 2016 at 21:34):
Wooo! Thanks Josh. May I request a publish to the npm registry so my team can start using it?
Josh Mandel (Apr 06 2016 at 02:26):
I think @nicola is the only one who can currently publish -- we should fix that too.
nicola (RIO/SS) (Apr 06 2016 at 04:34):
@Josh Mandel you can publish too
nicola (RIO/SS) (Apr 06 2016 at 05:09):
I've setup publishing on new tags by travis (i.e. npm will be published on every tag in github). Only minor problem - you have to manually update version in package.json, this potentially also could be automated.
Cole Diffin (Apr 07 2016 at 00:52):
Automated versioning is typically a bad idea - Its really hard to follow semantic versioning when the repo gets versioned without user input.
Cole Diffin (Apr 07 2016 at 00:52):
npm version [patch|minor|major] && git push && git push --tags is the pattern we use here for publishing.
Cole Diffin (Apr 07 2016 at 00:53):
Oh - Thanks for publishing :-)
nicola (RIO/SS) (Apr 07 2016 at 18:08):
We are talking about automatic publishing and making it DRY as possible - i.e. you only have to tag your version in one place github and all routine job is done for you by bots :)
Cole Diffin (Apr 07 2016 at 21:38):
Oh Ok :-) Sounds good.
Last updated: Apr 12 2022 at 19:14 UTC
