Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork966
Bump git/ext/gitdb from4c63ee6 to5c1b303#2106
Conversation
EliahKagan left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
EliahKagan commentedMar 9, 2026
@dependabot rebase |
Bumps [git/ext/gitdb](https://github.com/gitpython-developers/gitdb) from `4c63ee6` to `5c1b303`.- [Release notes](https://github.com/gitpython-developers/gitdb/releases)- [Commits](gitpython-developers/gitdb@4c63ee6...5c1b303)---updated-dependencies:- dependency-name: git/ext/gitdb dependency-version: 5c1b3036a6e34782e0ab6ce85e5ae64fe777fdbe dependency-type: direct:production...Signed-off-by: dependabot[bot] <support@github.com>
d8f2a05 to9648077Compare
EliahKagan left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
There are some further changes I may make soon in thegitdb and/orsmmap repositories. But I don't think they should block this. Aside from being unsure on the time frame for such changes, this is indirectly merging in changes corresponding to the newly released smmap 5.0.3. The changes there are minor, and the change that motivated the change was to metadata only, but I still think it makes sense to bring that in. (Note that this only affects the use of the submodules in test fixtures--that's the only remaining reason this repo has to have submodules. I still think it's worthwhile, though.)
I plan to merge this once CI passes.
c0a3d5f intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Bumpsgit/ext/gitdb from
4c63ee6to5c1b303.Commits
5c1b303Merge pull request#133 from gitpython-developers/dependabot/submodules/gitdb...af034fcBump gitdb/ext/smmap from5ec977atoe4ad410Dependabot 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)