-
Notifications
You must be signed in to change notification settings - Fork 39
Update dependencies to enable Greenkeeper 🌴 #117
Conversation
…es/Pages.Web/yarn.lock
…nLogs/AdminLogs.Web/yarn.lock
…s/Roles.Web/yarn.lock
…s/Sites.Web/yarn.lock
…es/Themes.Web/yarn.lock
…s/Users.Web/yarn.lock
…s/Users.Web/src/_exportables/yarn.lock
…tensions/Extensions.Web/yarn.lock
…censing/Licensing.Web/yarn.lock
…teImportExport/SiteImportExport.Web/yarn.lock
…teSettings/SiteSettings.Web/yarn.lock
…skScheduler/TaskScheduler.Web/yarn.lock
…cabularies/Vocabularies.Web/yarn.lock
…naBar/Bundle.Web/yarn.lock
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - Need to determine how we might approve the CLA for the bot?
@mitchelsellers I think we'd just need to make an exception for this service and merge it without. We could also try and contact them to see if they have anyway to handle such a request. |
@ohine Agreed, we are unable to get the GreenKeeper bot to actually agree to the CLA, so we just have to manually approve. |
Hi @mitchelsellers , @ohine! |
That’s correct. Are you in our slack group? We have a conversation going in the admin-experience channel with a guide to go over all the required changes. If you’d like to help out, make sure to coordinate with the team since everyone is working on a different AE project. |
DNN-10461 - Put dnn-tree-control-interactor on webpack
Let’s get started with automated dependency management for Dnn.AdminExperience 💪
🔒 Greenkeeper has found a
yarn.lock
file in this repository. Greenkeeper supports lockfile updates for public packages. If you use private packages in your repository, please use greenkeeper-lockfile to make sure these can get updated as well.This pull request updates all your dependencies to their latest version. Having them all up to date really is the best starting point for keeping up with new releases. 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.
Important: Greenkeeper will only start watching this repository’s dependency updates after you merge this initial pull request.
📦 📦 Greenkeeper has detected multiple
package.json
files. They have all been added to a newgreenkeeper.json
config file. They’ve been collected in a group calleddefault
, meaning that all of them will receive updates together. You can rename, add and remove groups and freely assign eachpackage.json
to whichever group you like. It’s common, for example, to have onefrontend
group and onebackend
group, each with a couple ofpackage.json
files. In any case, all files in a group will have their updates collected into single PRs and issues.🏷 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 👉![Greenkeeper badge](https://camo.githubusercontent.com/46a1b148e9dfb0a593a5fad7033ab16691420ab4db023f692eb00477d878379c/68747470733a2f2f6261646765732e677265656e6b65657065722e696f2f646e6e736f6674776172652f446e6e2e41646d696e457870657269656e63652e737667)
🏗 How to configure Travis CI
Greenkeeper has added a rule to your
.travis.yml
that whitelists Greenkeeper branches, which are created when your dependencies are updated. Travis CI will run your tests on these branches automatically to see if they still pass.No additional setup is required 😊
🙈 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.To make sure Greenkeeper doesn’t nag you again on the next update, add a
greenkeeper.ignore
field to yourpackage.json
, containing a list of dependencies you don’t want to update.👩💻 How to update this pull request
✨ 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.
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 .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.
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: :shipit:](https://github.githubassets.com/images/icons/emoji/shipit.png)
To get a better idea of which ranges apply to which releases, check out the extremely useful semver calculator provided by npm.
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Good luck with your project and see you soon ✨
Your Greenkeeper bot 🌴