Skip to content
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.

chore(deploy): upgrade to node 10 #477

Merged
merged 2 commits into from
Feb 20, 2019
Merged

chore(deploy): upgrade to node 10 #477

merged 2 commits into from
Feb 20, 2019

Conversation

philbooth
Copy link
Contributor

Fixes #476.

Updates the dockerfile and circle to use node 10 images. Also updates nyc because of the handlebars nsp advisory. Didn't get any problems updating, so not sure what I did differently to @shane-tomlinson after he mentioned something in the meeting yesterday.

I figured we could try this for train 131? Otherwise there's nothing in master that merits tagging a new release.

@mozilla/fxa-devs r?

@philbooth philbooth self-assigned this Feb 20, 2019
@philbooth philbooth requested a review from a team February 20, 2019 11:16
@philbooth
Copy link
Contributor Author

Otherwise there's nothing in master that merits tagging a new release.

That didn't come out right. I meant that with nothing else in the release, it might be a good juncture to upgrade the node version.

@philbooth
Copy link
Contributor Author

Actually, scratch that, let's aim for 132 so we can run node 10 in local dev for a couple of weeks first.

Copy link
Contributor

@vladikoff vladikoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@philbooth philbooth merged commit 96b548b into master Feb 20, 2019
@philbooth philbooth deleted the pb/node-10 branch February 20, 2019 14:50
@@ -1,8 +1,6 @@
language: node_js

node_js:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the difference between what you and I did, I kept node 8 here and it blew up.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It worked when that was still in there too fwiw, I only took it out after @vladikoff mentioned something in the auth server PR.

I thought maybe you forgot to update shrinkwrap and that overrode the optional dependencies or something?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants