Conversation
Bumps [gitpython](https://github.com/gitpython-developers/GitPython) from 3.1.30 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.30...3.1.32) --- updated-dependencies: - dependency-name: gitpython dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
facebook-github-bot
added
the
CLA Signed
JiwaniZakir
left a comment
JiwaniZakir
left a comment
There was a problem hiding this comment.
The bump in requirements.txt from GitPython==3.1.30 to GitPython==3.1.32 addresses CVE-2023-41040 (a directory traversal vulnerability) and CVE-2023-40590 (a remote code execution risk via .git config injection), so the security motivation is sound. However, pinning to an exact version (==3.1.32) means the project won't automatically absorb future security patches — consider using >=3.1.32 with an upper bound if the API surface used by MMF is stable across minor releases. It's also worth checking whether the tqdm>=4.43.0,<4.50.0 and requests==2.23.0 pins nearby are similarly outdated, since a targeted version bump like this is a good opportunity to audit adjacent dependencies. Finally, there are no tests or CI notes confirming that the GitPython-dependent code paths (e.g., any git-based dataset download or version introspection utilities in the codebase) were exercised against the new version before merging.
2 participants
Bumps gitpython from 3.1.30 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.