In this example, the new version 4.0.0 is not included in the old ^3.0.0 range.įor version updates like these – let’s call them “out of range” updates – you’ll receive a pull request. 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. This way, you’ll never be surprised by a dependency breaking your code. However, should the tests fail, Greenkeeper will create an issue to inform you about the problem immediately. When the test services report success Greenkeeper will silently delete the branch again, because no action needs to be taken – everything is fine. 1.7.0 is included in the old ^1.6.0 range, because of the caret ^ character. The above example shows an in-range update. 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.
The branch creation should trigger your testing services and check whether your code still works with the new dependency version. ✨ How do dependency updates work with Greenkeeper?Īfter you merge this pull request, Greenkeeper will create a new branch whenever a dependency is updated, with the new version applied. Git commit -m 'chore: adapt code to updated dependencies' # Adapt your code until everything works again
?? How to update this pull request # Change into your repository’s directory 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. In this case, you can change the dependency’s version string in the package.json file back to whatever you prefer. You may have good reasons for not wanting to update to a certain dependency right now. This is what your badge looks like right now :point_right: ? How to ignore certain dependencies Greenkeeper adds a badge to your README which indicates the status of this repository. ? How to check the status of this repository Then push your changes to this branch and merge it. next-update is a really handy tool to help you with this. Then fix your code to accomodate the changes in the updated dependency. To solve the issue, first find out which of the dependency’s updates is causing the problem. Important: Greenkeeper will only start watching this repository’s dependency updates after you merge this initial pull request. Greenkeeper will look out for further dependency updates and make sure to handle them in isolation and in real-time, but only after you merge this pull request. Having them all up to date really is the best starting point for keeping up with new releases. This pull request updates all your dependencies to their latest version. Let’s get started with automated dependency management for favesound-redux :muscle:
At the end it is a perfect project to get started in open source! Improveįeedback is more than appreciated via GitHub or Twitter GitHub
Moreover I will try to find the time to raise some more issues where people can contribute. I would love to see a GitHub issue to see where you want to work on. Rather I see more value in improving the status quo of the app: Improving the player, the playlist or the interaction overall. I wouldn't want to extend the project with new routes like: that's my profile page and that's my favorite track page. I am looking actively for contributors to make this project awesome!