semantic-release@next about semantic-release

[boennemann]

Pinging a few people that I think could be interested (also feedback would be cool :))
@christophwitzko @janl @gr2m @othiym23 @rmehner @remy @tlvince

[rmehner]

The Travis deploy integration with npm is so bad, that we need to do it ourselves anyways. Namely auth, where it still uses the old base64 encoded username and password, but also one can't pass arguments to the publish command itself.

I'm a bit undecided on that. My first thought about this was: Why not fix the npm integration of Travis so that all other unrelated projects can benefit from that? I know that Travis is essentially a product that we'd improve there, but they're good citizens and so is npm inc. You know better than I do what's wrong with the integration, but happy to discuss that and help out with some of my Ruby skills if needed.

[gr2m]

I had the same thought as @rmehner: any chance we could help fix travis instead? Or is it a conceptual issue?

[boennemann]

@rmehner @gr2m This sounded way to bold. Doing it on our own essentially means setting an encrypted env var with the npm token, creating an ~/.npmrc and running npm publish on after_success. (npm@^2.0.0 required)

The ~/.npmrc

registry=https://registry.npmjs.org/
//registry.npmjs.org/:_authToken=${NPM_TOKEN}

I want to build this for semantic-release first, so there are no blockers. I am more than happy to bring this back to Travis then. (Same goes for the npm team, as they want to get rid of the old token). The dpl tool is open source anyway: https://github.com/travis-ci/dpl/blob/master/lib/dpl/provider/npm.rb

[janl]

I’m generally +1 on all of this :)