I hereby claim:
- I am maxrimue on github.
- I am maxrimue (https://keybase.io/maxrimue) on keybase.
- I have a public key whose fingerprint is B9CE 163C 530D 4B14 35B7 F5E9 D71C 1093 734A 26AF
To claim this, I am signing this object:
#!/bin/bash | |
# Assume we have two semantic versions that we want to compare: | |
version1=0.12.0 | |
version2=1.15.5 | |
# First, we replace the dots by blank spaces, like this: | |
version1=${version1//./ } |
I hereby claim:
To claim this, I am signing this object:
When using yarn, it will create a yarn.lock
lockfile which holds data on your used dependencies. This file also includes hard-typed versions, so should you update your dependencies, the yarn.lock
file is basically outdated and needs to be regenerated. While yarn does this automatically, Greenkeeper pull requests that update dependencies as of right now do not do this regeneration, which means you would have to do it manually.
This gist shows you a way how to automatise this step using a Travis CI script.
yarn.lock
file in your repository for Travis CI to automatically install yarn (yarn will be added to their default images soon)