Pin dependencies #26

Merged
merged 1 commit into from Apr 19, 2016

Projects

None yet

3 participants

@kvz
Contributor
kvz commented Jan 11, 2016

This helps against things suddenly exploding in your face, such as our deploys today because xmldom slipped a not-so-backwards-compatible update in a patch version. Who can blame them, it's impossible to know all the different ways people are using your project and what effects a minor change might have, and how that might break things in subtle or not so subtle ways for them.

Long story short, let's pin dependencies so any change is explicit & tested, and our builds and deploys are reproducible.

See #25

@sbstnmsch

This fixes #25 for me. +1 for merging this into 1.0.5

@Pavliko
Owner
Pavliko commented Apr 19, 2016

Thank you for your job 👍

@Pavliko Pavliko merged commit 4d3c58f into Pavliko:master Apr 19, 2016
@sbstnmsch

Just my recommendation - using travis-ci together with greenkeeper.io will automagically test and PR when new versions arrive on NPM - keeping everything green and up-to-date. Maybe i have time to spent on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment