Bump gitpython from 3.1.43 to 3.1.52 in /llvm/utils/git - #21
Bump gitpython from 3.1.43 to 3.1.52 in /llvm/utils/git#21dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [gitpython](https://github.com/gitpython-developers/GitPython) from 3.1.43 to 3.1.52. - [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.43...3.1.52) --- updated-dependencies: - dependency-name: gitpython dependency-version: 3.1.52 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Hello @dependabot[bot] 👋 Thank you for submitting a Pull Request (PR) to the LLVM Project. Since this is your first PR, here are a few useful links covering our main contribution policies and review practices.
Please reply to this message to confirm that you have read these policies, especially the LLVM AI Tool Use Policy, and that any AI tool usage has been noted in the PR description. Frequently asked questionsHow do I add reviewers? This PR will be automatically labeled, and the relevant teams will be notified. For some parts of the project, reviewers may also be added automatically. You can also add reviewers manually using the Reviewers section on this page. If you cannot use that section, it is probably because you do not have write permissions for the repository. In that case, you can request a review by tagging reviewers in a comment using What if there are no comments? If you have not received any comments on your PR after a week, you can request a review by pinging the PR with a comment such as “Ping”. The common courtesy ping rate is once a week. Please remember that you are asking for volunteer time from other developers. Are any special GitHub settings required to contribute to LLVM? We only require contributors to have a public email address associated with their GitHub commits, see this section of LLVM Developer Policy for details. If you have questions, feel free to leave a comment on this PR, or ask on LLVM Discord or LLVM Discourse. Thank you, |
|
Superseded by #25. |
Bumps gitpython from 3.1.43 to 3.1.52.
Release notes
Sourced from gitpython's releases.
... (truncated)
Commits
f8b6df5bump patch level prior to releasec65dfb3Merge pull request #2172 from gitpython-developers/fix-clone-expandvars8ac5a30fix: prevent environment expansion in clone URLs7a46dfcMerge pull request #2171 from gitpython-developers/fix-windows-tests67082d6test: skip relative config include across Windows drives7b0764dbump to v3.1.51af027beMerge pull request #2163 from gitpython-developers/fix-unguarded-blame701ce32fix: Guard unsafe git command options (GHSA-956x-8gvw-wg5v)65a7283Merge pull request #2168 from gitpython-developers/advisory-fix-13e59876Merge pull request #2169 from gitpython-developers/fix-config-assertDependabot 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 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.