Letâs get started with automated dependency management for backend-data :muscle:
All of your dependencies are already up-to-date, so this repository was enabled right away. Good job :thumbsup:
đˇ How to check the status of this repository
Greenkeeper adds a badge to your README which indicates the status of this repository.
This is what your badge looks like right now :point_right: 
đ How to ignore certain dependencies
You may have good reasons for not wanting to update to a certain dependency right now. In this case, you can [change the dependencyâs version string in the `package.json` file back to whatever you prefer](https://github.com/vpapp-team/backend-data/edit/greenkeeper/initial/package.json).
To make sure Greenkeeper doesnât nag you again on the next update, add a `greenkeeper.ignore` field to your `package.json`, containing a list of dependencies you donât want to update.
```js
// package.json
{
âŚ
"greenkeeper": {
"ignore": [
"package-names",
"you-want-me-to-ignore"
]
}
}
```
đŠâđť How to update this pull request
```bash
# Change into your repositoryâs directory
git fetch --all
git checkout greenkeeper/initial
npm install-test
# Adapt your code until everything works again
git commit -m 'chore: adapt code to updated dependencies'
git push https://github.com/vpapp-team/backend-data.git greenkeeper/initial
```
⨠How do dependency updates work with Greenkeeper?
After you merge this pull request, **Greenkeeper will create a new branch whenever a dependency is updated**, with the new version applied. The branch creation should trigger your testing services and check whether your code still works with the new dependency version. Depending on the the results of these tests Greenkeeper will try to open meaningful and helpful pull requests and issues, so your dependencies remain working and up-to-date.
```diff
- "underscore": "^1.6.0"
+ "underscore": "^1.7.0"
```
The above example shows an in-range update. `1.7.0` is included in the old `^1.6.0` range, because of the [caret `^` character ](https://docs.npmjs.com/misc/semver#ranges).
When the test services report success Greenkeeper will silently delete the branch again, because no action needs to be taken â everything is fine.
However, should the tests fail, Greenkeeper will create an issue to inform you about the problem immediately.
This way, youâll never be surprised by a dependency breaking your code. As long as everything still works, Greenkeeper will stay out of your way, and as soon as something goes wrong, youâll be the first to know.
```diff
- "lodash": "^3.0.0"
+ "lodash": "^4.0.0"
```
In this example, the new version `4.0.0` is _not_ included in the old `^3.0.0` range.
For version updates like these â letâs call them âout of rangeâ updates â youâll receive a pull request.
This means that **you no longer need to check for new versions manually** â Greenkeeper will keep you up to date automatically.
These pull requests not only serve as reminders to update: If you have solid tests and good coverage, and the pull requests passes those tests, you can very likely just merge it and release a new version of your software straight away :shipit:
To get a better idea of which ranges apply to which releases, check out the extremely useful [semver calculator](https://semver.npmjs.com/) provided by npm.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donât help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Good luck with your project and see you soon :sparkles:
Letâs get started with automated dependency management for backend-data :muscle:
All of your dependencies are already up-to-date, so this repository was enabled right away. Good job :thumbsup:
đˇ How to check the status of this repository
Greenkeeper adds a badge to your README which indicates the status of this repository. This is what your badge looks like right now :point_right: đ How to ignore certain dependencies
You may have good reasons for not wanting to update to a certain dependency right now. In this case, you can [change the dependencyâs version string in the `package.json` file back to whatever you prefer](https://github.com/vpapp-team/backend-data/edit/greenkeeper/initial/package.json). To make sure Greenkeeper doesnât nag you again on the next update, add a `greenkeeper.ignore` field to your `package.json`, containing a list of dependencies you donât want to update. ```js // package.json { ⌠"greenkeeper": { "ignore": [ "package-names", "you-want-me-to-ignore" ] } } ```đŠâđť How to update this pull request
```bash # Change into your repositoryâs directory git fetch --all git checkout greenkeeper/initial npm install-test # Adapt your code until everything works again git commit -m 'chore: adapt code to updated dependencies' git push https://github.com/vpapp-team/backend-data.git greenkeeper/initial ```⨠How do dependency updates work with Greenkeeper?
After you merge this pull request, **Greenkeeper will create a new branch whenever a dependency is updated**, with the new version applied. The branch creation should trigger your testing services and check whether your code still works with the new dependency version. Depending on the the results of these tests Greenkeeper will try to open meaningful and helpful pull requests and issues, so your dependencies remain working and up-to-date. ```diff - "underscore": "^1.6.0" + "underscore": "^1.7.0" ``` The above example shows an in-range update. `1.7.0` is included in the old `^1.6.0` range, because of the [caret `^` character ](https://docs.npmjs.com/misc/semver#ranges). When the test services report success Greenkeeper will silently delete the branch again, because no action needs to be taken â everything is fine. However, should the tests fail, Greenkeeper will create an issue to inform you about the problem immediately. This way, youâll never be surprised by a dependency breaking your code. As long as everything still works, Greenkeeper will stay out of your way, and as soon as something goes wrong, youâll be the first to know. ```diff - "lodash": "^3.0.0" + "lodash": "^4.0.0" ``` In this example, the new version `4.0.0` is _not_ included in the old `^3.0.0` range. For version updates like these â letâs call them âout of rangeâ updates â youâll receive a pull request. This means that **you no longer need to check for new versions manually** â Greenkeeper will keep you up to date automatically. These pull requests not only serve as reminders to update: If you have solid tests and good coverage, and the pull requests passes those tests, you can very likely just merge it and release a new version of your software straight away :shipit: To get a better idea of which ranges apply to which releases, check out the extremely useful [semver calculator](https://semver.npmjs.com/) provided by npm.FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donât help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Good luck with your project and see you soon :sparkles:
Your Greenkeeper bot :palm_tree: