-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Enable dependabot updates #11828
Comments
We would like to take advantage of Dependabot, but the first order of business is to use a dependency specification and formal lockfile: #11537. |
@DMRobertson Okay, good to know. Thanks for the quick response |
We have dependabot PRing security updates now that we use locked dependencies. Next steps would be to
Last time we talked about this I think there was general agreement this was probably worthwhile? We already test against latest deps in CI and this pulls in useful bugfixes (e.g. recent frozendict memory leak fixes.) |
@DMRobertson Good to hear. Dependabot can be configured quite easily (see: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates). For myself, Dependabot takes some of the work off my hands as it keeps track of (non-)security upgrades and notifies me once a month (can be configured as desired). For larger projects or organizations this could be done daily or weekly (see: https://github.com/cinnyapp/cinny/blob/dev/.github/dependabot.yml) |
This claims to fix more memory leaks. Could have automated this upgrade with #11828 if we wanted.
* Update frozendict 2.3.3 -> 2.3.4 This claims to fix more memory leaks. Could have automated this upgrade with #11828 if we wanted. * Changelog
Description:
I already use Dependabot for many projects. With Dependabot it is relatively easy to stay up to date with the dependencies and packages used. Instead of always checking for updates manually, you can e.g. use the dependabot.yml configuration to tell Dependabot to check the project once a week for new releases of the Python packages that are used. If there are new updates, a new pull request is automatically created for them.
Since this procedure takes at least some work off my hands over at my projects, I wanted to ask if you would be up to using it as well. The configuration file is quickly created and dependabot then runs without further ado.
The text was updated successfully, but these errors were encountered: