-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more regular updates of dependencies #15
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Remove video
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
I think the reporter has a fair point. We're also depending on this template as a reference point. |
/lifecycle frozen |
This is a template repository, so many will start off of this. I think you, therefore, have an extra responsibility to have your dependencies up to date so others don't start off with out-of-date dependencies.
There are some great tools to help you keep your dependencies up to date with pretty low effort, here are a couple of examples:
Both of these support auto-merge of pull requests (either by GitHub actions or by Renovatebot App), so you can for example auto-merge all minor and patch versions to keep the maintenance low. You seem to have good testing in this project, so you can be confident you don't break the project.
The text was updated successfully, but these errors were encountered: