security(deps): bump gitpython from 3.1.57 to 3.1.58 in /training/rl - #1343
security(deps): bump gitpython from 3.1.57 to 3.1.58 in /training/rl#1343dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [gitpython](https://github.com/gitpython-developers/GitPython) from 3.1.57 to 3.1.58. - [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.57...3.1.58) --- updated-dependencies: - dependency-name: gitpython dependency-version: 3.1.58 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsEnsure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice. OpenSSF Scorecard
Scanned Files
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1343 +/- ##
=======================================
Coverage 87.84% 87.84%
=======================================
Files 273 273
Lines 22331 22331
Branches 3066 3066
=======================================
Hits 19617 19617
Misses 2055 2055
Partials 659 659
*This pull request uses carry forward flags. Click here to find out more. 🚀 New features to boost your workflow:
|
Marcel Bindseil (bindsi)
left a comment
There was a problem hiding this comment.
Advisory Review Summary
- Ecosystem:
uv/ PyPI - Surface:
python-runtimeundertraining/rl; Isaac Lab runtime lock - Reviewed against actual GitHub base
41270d2d19c6366284c2e979584c9d33c0cb498aand headc55e7958905c0984b391b028b6fe288dc1ca8518 - Technical verdict: MERGE
- Confidence: High
- Blocking findings: None
| Package | From | To | Severity | Surface |
|---|---|---|---|---|
| GitPython | 3.1.57 | 3.1.58 | 5 High, 1 Medium upstream draft advisories; no assigned CVEs in the cited upstream PRs | python-runtime / training-rl |
GitPython
Advisory summary
- Upstream GitPython PR #2204 identifies five draft advisories affecting
<=3.1.57: four High and one Medium, covering config syntax injection, unsafe joined options,read-treeindex output, unsafeRepo.initoptions, and pathspec-file input. The fixes retainallow_unsafe_options=Truefor explicitly trusted callers. - Upstream GitPython PR #2202 identifies one additional High draft advisory affecting
<=3.1.57and adds validation for empty, rooted, drive-qualified, and parent-component submodule names. - Those six GHSA records are not yet public through GitHub's global advisory endpoint, and no CVEs are assigned in the upstream PR descriptions. OSV queries for both 3.1.57 and 3.1.58 returned no published records, so no CVSS/CWE claims are inferred here.
Release and compatibility evidence
“Validate submodule names before filesystem operations” and “Harden config and Git option validation.”
The official 3.1.58 release was published on 2026-08-04 as a non-prerelease security/fix release. PyPI metadata confirms version 3.1.58 is published and non-yanked, provides a universal py3-none-any wheel plus sdist, requires Python >=3.7, and retains the runtime dependency gitdb>=4.0.1,<5. The lock keeps gitdb==4.0.12.
Repository-specific risk
- The direct pin changes only at
training/rl/pyproject.toml:18. - The head lock preserves Python 3.11 and the single Linux x86_64 universal-lock target at
training/rl/uv.lock:3-9, records GitPython 3.1.58 attraining/rl/uv.lock:502-508, and aligns the root requirement attraining/rl/uv.lock:1545. - Full-diff inspection found no package-version changes other than GitPython and no artifact/hash changes outside its wheel/sdist. The remaining lock churn removes redundant Linux x86_64 markers from dependency edges while leaving the lock's top-level
resolution-markersandsupported-markersunchanged. - Isaac Lab constraints remain intact:
requires-python ==3.11.*andnumpy==1.26.4are unchanged; no Torch, TensorDict, ONNX Runtime, NumPy, or CUDA package version changed. The frozen installer still excludes container-provided Torch/CUDA packages insetup_isaac_runtime.sh. - GitHub code search found no training Python call sites using
Repo.clone_from,multi_options, orallow_unsafe_options. The runtime behavior changes are security validation failures for unsafe inputs, not an API/dependency removal used by repository-owned training code.
Validation Signal
- Deterministic CI:
PR Validation: success; all per-surface check-runs passed. Relevant green checks include uv Lock Consistency, Pytest Training, RL CPU Import Smoke, RL Runtime-Image Smoke, Python Lint, Dependency Review, and OSV-Scanner. - Static impact reasoning: the Isaac Sim ABI guard is satisfied because NumPy remains 1.26.4, below 2.0, and the lock's Python/platform target is unchanged. The runtime-image smoke check exercised the affected RL environment successfully.
- GitHub currently reports
mergeable_state: blocked, consistent with required repository review policy rather than a failing check.
Advisory recommendation: Maintainer review recommended because this release patches multiple upstream-documented High-severity draft advisories; no technical blocker remains after the green lock, training, and runtime-image validation.
|
Dependabot (@dependabot) rebase |
|
Looks like gitpython is up-to-date now, so this is no longer needed. |
Bumps gitpython from 3.1.57 to 3.1.58.
Release notes
Sourced from gitpython's releases.
Commits
30be45dprepare changelog for upcoming releasefc2f02cMerge pull request #2197 from Cyrus580529/shared-symlink-guardb10e250test: use the shared guard instead of local copiese3e5da8test: skip tests that need symlink privileges30d05e3test: add a shared symlink capability guard9a8f6feMerge pull request #2204 from gitpython-developers/security-fixesf2550b6Guard pathspec file inputs in high-level commandsd9ddb55Guard unsafe git init options9b5dcafGuard read-tree index output paths96a888fCheck joined short-option values before Git executionDependabot 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.