-
Notifications
You must be signed in to change notification settings - Fork 592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
maintenance: add auto-updating of npm packages #1626
maintenance: add auto-updating of npm packages #1626
Conversation
@@ -52,7 +52,7 @@ | |||
"dependencies": { | |||
"@google-cloud/common": "^0.5.0", | |||
"arrify": "^1.0.0", | |||
"dns-zonefile": "0.1.18", | |||
"dns-zonefile": "^0.1.18", |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Changes Unknown when pulling 14a34bd on stephenplusplus:spp--update-all into * on GoogleCloudPlatform:master*. |
'use strict'; | ||
|
||
var async = require('async'); | ||
var david = require('david'); |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
So what's the long term plan for this? Run it once in a while to see if we have updates..? I think it would be great it we could tie this into CI somewhere and have it just run weekly or so..? |
That's interesting. My plan was to simply run it manually before publishing. |
This script will update our sub-modules to the latest compatible dependencies when run:
Also included in the PR are the modified package.json's after running.