build(deps-dev): bump gitpython from 3.1.31 to 3.1.32 #86
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [gitpython](https://github.com/gitpython-developers/GitPython) from 3.1.31 to 3.1.32. - [Release notes](https://github.com/gitpython-developers/GitPython/releases) - [Changelog](https://github.com/gitpython-developers/GitPython/blob/main/CHANGES) - [Commits](gitpython-developers/GitPython@3.1.31...3.1.32) --- updated-dependencies: - dependency-name: gitpython dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## main #86 +/- ##
=======================================
Coverage 90.78% 90.78%
=======================================
Files 24 24
Lines 1389 1389
Branches 245 245
=======================================
Hits 1261 1261
Misses 93 93
Partials 35 35
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
@marcofavorito @francescofuggitti What should we do with this and #85 ? In general, not sure what the best protocol is for these security-specific pipfile.lock stuff. |
The protocol should be as easy as merging the PR, so to keep However, handling multiple PR is not straightforward since when one is merged, the changes to the There is a feature request for merging the dependabot PRs into one: dependabot/dependabot-core#2265, but it seems blocked. Another issue is that the current notification is for Not sure how to proceed from here. On the one hand, having the dependabot working will periodically notify us about some missing upgrades; this will require to process the PR periodically (either by hand, or merging-rebasing the PRs one by one). On the other hand, if we keep dependabot, we would have the PR page a bit dirty, without great benefits: in the end, |
|
Superseded by #88. |
Bumps gitpython from 3.1.31 to 3.1.32.
Release notes
Sourced from gitpython's releases.
Commits
5d45ce2prepare 3.1.32 releaseca965ecMerge pull request #1609 from Beuc/block-insecure-options-clone-non-multi5c59e0dBlock insecure non-multi options in clone/clone_fromc09a71eMerge pull request #1606 from r-darwish/no-dela3859eefixes8186159Don't rely on del741edb5Merge pull request #1603 from eUgEntOptIc44/eugenoptic44-fix-pypi-long-descri...0c543cdImprove readability of README.md9cd7ddbImprove the 'long_description' displayed on pypi6fc11e6update README to reflect the status quo ongitcommand usageDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.