-
Notifications
You must be signed in to change notification settings - Fork 85
Migrate to Circle CI 2.0 #77
Conversation
steps: | ||
- checkout | ||
- restore_cache: | ||
key: dependency-cache-{{ checksum "package.json" }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should probably switch to yarn here at some point.
Circle CI v1 is shutting down on August 31st. This migrates the configuration to Circle 2.0. There should be no functional changes, though we should consider using yarn at some point.
- test | ||
filters: | ||
tags: | ||
only: /[0-9]+(\.[0-9]+)*(-.+)?/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ccnixon @Peripheral1994 would love to get some on eyes on this part to ensure we're only deploying under two conditions (as before):
- branch is master
- version is tagged
cc @fathyb |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! 💯
jobs: | ||
test: | ||
docker: | ||
- image: circleci/node:4-browsers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Node.js 4 has been dropped and 6 is in maintenance since April. We should consider upgrading to 8 (current LTS).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes absolutely! I wanted to avoiding changing too much in this PR, but I think that's a great point. I'll make a ticket for this in the backlog.
This slipped through in the previous PR (#77).
Circle CI v1 is shutting down on August 31st. This migrates the configuration to Circle 2.0.
There should be no functional changes.