Add auto-release #8
Conversation
|
( I've just given the engineering team write access to the repo 👍 ) |
damassi
force-pushed
the
add-auto-release
branch
from
c848165
to
5bd9404
Compare
|
So, I'm going to do the work here, but I ain't mergin' this one, ha. |
|
A few things here... I moved the CI over to Circle. I know it's massively more complex, but it brings it in line with our other setups. I added the danger job to the circle config. May need to tweak the caching a little bit b/c the CI isn't going to actually run until that's merged into master. I could technically pull it out into a separate PR (likely the right thing to do), but being as it's pretty much a copy and paste of palette's setup I'm reasonably certain it'll work fine. |
| @@ -5,10 +5,13 @@ | |||
| "main": "build/index.js", | |||
| "author": "Eloy Durán <eloy.de.enige@gmail.com> & Art.sy Inc", | |||
| "license": "MIT", | |||
| "publishConfig": { | |||
| "registry": "https://registry.npmjs.org/" | |||
| }, | |||
There was a problem hiding this comment.
Because we're using yarn it defaults to their alias registry and always fails. Took @orta a minute to track that one down originally.
There was a problem hiding this comment.
Related to Circle or Auto?
There was a problem hiding this comment.
Auto. It's from this commit artsy/reaction@46b686c.
Adds auto-release as a replacement for
semantic-release.(Will remove release-it in a follow-up PR.)
Related: