Update all dependencies 🌴

[greenkeeperio-bot]

Hello 👋

This is the first automated pull requests to help reach the goal of up to date and stable software.
It updates all of the dependencies in the package.json in one go, but from now on you’ll receive pull requests for each dependency update in isolation and in real time.

For updates that satisfy the existing version range you’ll get pull-requests only if it breaks your build.

Example:

-  "underscore": "^1.6.0"
+  "underscore": "^1.7.0"

When an update does not satisfy the existing range you’ll get the pull request right away.

Example:

-  "lodash": "^3.0.0"
+  "lodash": "^4.0.0"

Happy fixing and merging 🌴

[zeke]

Hey @ashleygwilliams I love @greenkeeperio-bot, but it might not be a great fit for marky-markdown in its current state, as a ton of the devDependencies are really just used as test fixtures. Changes to their READMEs are likely to break the tests.

We could work around this by using a different technique to collect fixture data, but maybe there's an easier way.

@janl is there a way to configure greenkeeper to ignore devDependencies?

[zeke]

Hmm I guess we could just lock down the version numbers too.. Would that do it?

[ashleygwilliams]

hey @zeke maybe we should have those as bundled deps then? or just static fixtures?

[zeke]

Using bundleDependencies is not ideal because it will bloat the published package and pass along a bunch of stuff that end-users don't need.

Static fixtures would be the best option, I think. Just need a convenient way to download them. npm-cdn could be handy for fetching all the READMEs.

[ashleygwilliams]

since we don't need to fetch dynamically, i think just cut+paste should be fine? i dont think adding 2-3 md files to the package is too serious. but perhaps i am mistaken?

[zeke]

Yeah cut and paste would totally work! Was just trying to think of a way to automate that effort :)

dont think adding 2-3 md files to the package is too serious

Not worried about markdown files.. I just didn't want to bundle a bunch of entire packages, which is the effect using bundleDependencies would have (I think).

[ashleygwilliams]

yarp-- you wanna PR @zeke ? i want to cut 5.6 tonight, but i could be convinced to wait til tomorrow morning if you wanna sneak this in.

[ashleygwilliams]

ok this is gonna wait til 5.7

[zeke]

@ashleygwilliams I can take care of this, but probably not today. Congrats on shipping 6.0.0!

[janl]

Sorry, I’m only seeing this now; You can use the method described at greenkeeperio/greenkeeper#47 (comment) to have Greenkeeper ignore packages to update.

[ashleygwilliams]

closing per #114

[ashleygwilliams]

the only dep that wasn't eliminated by #114 was standard new pr for that here: #120