Update module github.com/go-git/go-git/v5 to v5.19.2 [SECURITY] - #58

Details

Impact

A path traversal vulnerability was discovered in go-git versions prior to v5.11. This vulnerability allows an attacker to create and amend files across the filesystem. In the worse case scenario, remote code execution could be achieved.

Applications are only affected if they are using the ChrootOS, which is the default when using "Plain" versions of Open and Clone funcs (e.g. PlainClone). Applications using BoundOS or in-memory filesystems are not affected by this issue.
This is a go-git implementation issue and does not affect the upstream git cli.

Patches

Users running versions of go-git from v4 and above are recommended to upgrade to v5.11 in order to mitigate this vulnerability.

Workarounds

In cases where a bump to the latest version of go-git is not possible in a timely manner, we recommend limiting its use to only trust-worthy Git servers.

Credit

Thanks to Ionut Lalu for responsibly disclosing this vulnerability to us.

Severity

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

References

• https://github.com/go-git/go-git/security/advisories/GHSA-449p-3h89-pw88
• https://nvd.nist.gov/vuln/detail/CVE-2023-49569
• https://github.com/advisories/GHSA-449p-3h89-pw88

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

Details

Impact

A denial of service (DoS) vulnerability was discovered in go-git versions prior to v5.11. This vulnerability allows an attacker to perform denial of service attacks by providing specially crafted responses from a Git server which triggers resource exhaustion in go-git clients.

Applications using only the in-memory filesystem supported by go-git are not affected by this vulnerability.
This is a go-git implementation issue and does not affect the upstream git cli.

Patches

Users running versions of go-git from v4 and above are recommended to upgrade to v5.11 in order to mitigate this vulnerability.

Workarounds

In cases where a bump to the latest version of go-git is not possible, we recommend limiting its use to only trust-worthy Git servers.

Credit

Thanks to Ionut Lalu for responsibly disclosing this vulnerability to us.

References

• GHSA-mw99-9chc-xw7r

Severity

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

References

• https://github.com/go-git/go-git/security/advisories/GHSA-mw99-9chc-xw7r
• https://nvd.nist.gov/vuln/detail/CVE-2023-49568
• https://github.com/advisories/GHSA-mw99-9chc-xw7r

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

Details

Impact

An argument injection vulnerability was discovered in go-git versions prior to v5.13.

Successful exploitation of this vulnerability could allow an attacker to set arbitrary values to git-upload-pack flags. This only happens when the file transport protocol is being used, as that is the only protocol that shells out to git binaries.

Affected versions

Users running versions of go-git from v4 and above are recommended to upgrade to v5.13 in order to mitigate this vulnerability.

Workarounds

In cases where a bump to the latest version of go-git is not possible, we recommend users to enforce restrict validation rules for values passed in the URL field.

Credit

Thanks to @​vin01 for responsibly disclosing this vulnerability to us.

Severity

• CVSS Score: 9.2 / 10 (Critical)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Clear

References

• https://github.com/go-git/go-git/security/advisories/GHSA-v725-9546-7q7m
• https://nvd.nist.gov/vuln/detail/CVE-2025-21613
• https://github.com/advisories/GHSA-v725-9546-7q7m

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

Details

Impact

A denial of service (DoS) vulnerability was discovered in go-git versions prior to v5.13. This vulnerability allows an attacker to perform denial of service attacks by providing specially crafted responses from a Git server which triggers resource exhaustion in go-git clients.

This is a go-git implementation issue and does not affect the upstream git cli.

Patches

Users running versions of go-git from v4 and above are recommended to upgrade to v5.13 in order to mitigate this vulnerability.

Workarounds

In cases where a bump to the latest version of go-git is not possible, we recommend limiting its use to only trust-worthy Git servers.

Credit

Thanks to Ionut Lalu for responsibly disclosing this vulnerability to us.

Severity

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

References

• https://github.com/go-git/go-git/security/advisories/GHSA-r9px-m959-cxf4
• https://nvd.nist.gov/vuln/detail/CVE-2025-21614
• https://github.com/advisories/GHSA-r9px-m959-cxf4

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

Details

Impact

A vulnerability was discovered in go-git whereby data integrity values for .pack and .idx files were not properly verified. This resulted in go-git potentially consuming corrupted files, which would likely result in unexpected errors such as object not found.

For context, clients fetch packfiles from upstream Git servers. Those files contain a checksum of their contents, so that clients can perform integrity checks before consuming it. The pack indexes (.idx) are generated locally by go-git, or the git cli, when new .pack files are received and processed. The integrity checks for both files were not being verified correctly.

Note that the lack of verification of the packfile checksum has no impact on the trust relationship between the client and server, which is enforced based on the protocol being used (e.g. TLS in the case of https:// or known hosts for ssh://). In other words, the packfile checksum verification does not provide any security benefits when connecting to a malicious or compromised Git server.

Patches

Users should upgrade to v5.16.5, or the latest v6 pseudo-version, in order to mitigate this vulnerability.

Workarounds

In case updating to a fixed version of go-git is not possible, users can run git fsck from the git cli to check for data corruption on a given repository.

Credit

Thanks @​N0zoM1z0 for finding and reporting this issue privately to the go-git project.

Severity

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

References

• https://github.com/go-git/go-git/security/advisories/GHSA-37cx-329c-33x3
• https://github.com/go-git/go-git/releases/tag/v5.16.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-25934
• https://github.com/advisories/GHSA-37cx-329c-33x3

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

Details

Impact

go-git’s index decoder for format version 4 fails to validate the path name prefix length before applying it to the previously decoded path name. A maliciously crafted index file can trigger an out-of-bounds slice operation, resulting in a runtime panic during normal index parsing.

This issue only affects Git index format version 4. Earlier formats (go-git supports only v2 and v3) are not vulnerable to this issue.

An attacker able to supply a crafted .git/index file can cause applications using go-git to panic while reading the index. If the application does not recover from panics, this results in process termination, leading to a denial-of-service (DoS) condition.

Exploitation requires the ability to modify or inject a Git index file within the local repository in disk. This typically implies write access to the .git directory.

Patches

Users should upgrade to v5.17.1, or the latest v6 pseudo-version, in order to mitigate this vulnerability.

Credit

go-git maintainers thank @​kq5y for finding and reporting this issue privately to the go-git project.

Severity

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

References

• https://github.com/go-git/go-git/security/advisories/GHSA-gm2x-2g9h-ccm8
• https://nvd.nist.gov/vuln/detail/CVE-2026-33762
• https://github.com/go-git/go-git/releases/tag/v5.17.1
• https://github.com/advisories/GHSA-gm2x-2g9h-ccm8

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

Details

Impact

A vulnerability has been identified in which a maliciously crafted .idx file can cause asymmetric memory consumption, potentially exhausting available memory and resulting in a Denial of Service (DoS) condition.

Exploitation requires write access to the local repository's .git directory, it order to create or alter existing .idx files.

Patches

Users should upgrade to v5.17.1, or the latest v6 pseudo-version, in order to mitigate this vulnerability.

Credit

The go-git maintainers thank @​kq5y for finding and reporting this issue privately to the go-git project.

Severity

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

References

• https://github.com/go-git/go-git/security/advisories/GHSA-jhf3-xxhw-2wpp
• https://github.com/go-git/go-git/releases/tag/v5.17.1
• https://nvd.nist.gov/vuln/detail/CVE-2026-34165
• https://github.com/advisories/GHSA-jhf3-xxhw-2wpp

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

Details

Impact

go-git may leak HTTP authentication credentials when following redirects during smart-HTTP clone and fetch operations.

If a remote repository responds to the initial /info/refs request with a redirect to a different host, go-git updates the session endpoint to the redirected location and reuses the original authentication for subsequent requests. This can result in the credentials (e.g. Authorization headers) being sent to an unintended host.

An attacker controlling or influencing the redirect target can capture these credentials and potentially reuse them to access the victim’s repositories or other resources, depending on the scope of the credential.

Clients using go-git exclusively with trusted remotes (for example, GitHub or GitLab), and over a secure HTTPS connection, are not affected by this issue. The risk arises when interacting with untrusted or misconfigured Git servers, or when using unsecured HTTP connections, which is not recommended. Such configurations also expose clients to a broader class of security risks beyond this issue, including credential interception and tampering of repository data.

Patches

Users should upgrade to v5.18.0, or v6.0.0-alpha.2, in order to mitigate this vulnerability. Versions prior to v5 are likely to be affected, users are recommended to upgrade to a supported go-git version.

The patched versions add support for configuring followRedirects. In line with upstream behaviour, the default is now initial, while users can opt into FollowRedirects or NoFollowRedirects programmatically.

Credit

Thanks to the 3 separate reports from @​celinke97, @​N0zoM1z0 and @​AyushParkara. Thanks for finding and reporting this issue privately to the go-git project. 🙇

Severity

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

References

• https://github.com/go-git/go-git/security/advisories/GHSA-3xc5-wrhm-f963
• https://nvd.nist.gov/vuln/detail/CVE-2026-41506
• https://github.com/go-git/go-git/releases/tag/v5.18.0
• https://github.com/go-git/go-git/releases/tag/v6.0.0-alpha.2
• https://github.com/advisories/GHSA-3xc5-wrhm-f963

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

Details

Impact

go-git may parse malformed Git objects in a way that differs from upstream Git. When commit or tag objects contain ambiguous or malformed headers, go-git’s decoded representation may expose values differently from how Git itself would interpret or reject the same object.

Additionally, go-git’s commit signing and verification logic operates over commit data reconstructed from go-git’s parsed representation rather than the original raw object bytes. As a result, go-git may sign or verify a commit payload that is not byte-for-byte equivalent to the object stored in the repository.

This can cause a signature to appear valid for a commit whose displayed or effective metadata differs from the object that was intended to be signed.

Patches

Users should upgrade to a patched version in order to mitigate this vulnerability. Versions prior to v5 are likely to be affected, users are recommended to upgrade to a supported go-git version.

Credit

Thanks to @​bugbunny-research (https://bugbunny.ai/) for reporting this to sigstore/gitsign, and to @​wlynch, @​patzielinski and @​adityasaky for coordinating the disclosure with the go-git project. 🙇 🥇

Thanks to @​wayphinder for reporting this to the go-git project. 🙇

Severity

• CVSS Score: 7.0 / 10 (High)
• Vector String: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N

References

• https://github.com/go-git/go-git/security/advisories/GHSA-389r-gv7p-r3rp
• https://nvd.nist.gov/vuln/detail/CVE-2026-45022
• https://github.com/advisories/GHSA-389r-gv7p-r3rp

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

Details

Impact

go-git's SSH transport constructs the remote exec command by wrapping the repository path in single quotes without escaping single quotes embedded inside the path. This diverges from canonical Git, which shell-quotes the path through sq_quote_buf so that an embedded ' becomes the '\'' close-escape-reopen sequence and the whole path round-trips as a single quoted argument.

A repository path containing a single quote can therefore break out of the quoted region in the exec command and be appended as additional shell tokens. On SSH servers that evaluate the exec command through a shell (for example a user account whose login shell is /bin/sh or /bin/bash, or a ForceCommand wrapper that re-evaluates $SSH_ORIGINAL_COMMAND), those additional tokens execute in that account's command-execution context. SSH servers that tokenize the exec command without shell evaluation, including the canonical git-shell setup, are not affected.

The vulnerable behaviour is on the SSH server side, not in go-git: the same bytes can be produced by any SSH client. The change in go-git is defense-in-depth that restores parity with canonical Git's wire format and prevents go-git from being a vehicle for reaching shell-evaluating servers through attacker-influenced repository paths.

Patches

Users should upgrade to a patched version in order to mitigate this issue. The fix ports sq_quote_buf from canonical Git into go-git's SSH transport so that the wire output is byte-identical to what git itself would send for the same input.

Versions prior to v5 are likely to be affected, users are recommended to upgrade to a supported go-git version.

Credit

Thanks to @​N0zoM1z0 for reporting this to the go-git project. 🙇

Severity

• CVSS Score: 2.3 / 10 (Low)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L

References

• https://github.com/go-git/go-git/security/advisories/GHSA-m7cr-m3pv-hgrp
• https://nvd.nist.gov/vuln/detail/CVE-2026-45570
• https://github.com/advisories/GHSA-m7cr-m3pv-hgrp

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

Details

Impact

A path validation issue in go-git could allow crafted repository data to affect files outside the intended checkout target, including the repository's .git directory.

These validations were introduced in upstream Git years ago, so the vulnerability arose from go-git drifting from those checks. Some attack vectors were platform-specific: certain payloads affected only Windows users, others affected only macOS users, and some applied across all supported platforms.

Using non-descendant go-billy filesystem instances, or different filesystem types, for the Storer and Worktree may provide some isolation against .git directory manipulation. For example, users that store the .git directory through memfs while using osfs for the worktree are not affected by this vulnerability in the main repository, because repository metadata is not materialized inside the worktree filesystem.

However, this isolation does not necessarily apply when the repository contains submodules, since submodule dotgit directories may still be represented or materialized within the worktree context.

It is important to note that exploitation requires a maliciously crafted repository payload. Users should always exercise caution when interacting with repositories or Git servers they do not trust.

Patches

Users should upgrade to a patched version in order to mitigate this vulnerability. Versions prior to v5 are likely to be affected, users are recommended to upgrade to a supported go-git version.

Credits

Thanks to @​kodareef5, @​AyushParkara and @​N0zoM1z0 for reporting this to the go-git project in three separate reports. 🙇

Severity

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

References

• https://github.com/go-git/go-git/security/advisories/GHSA-crhj-59gh-8x96
• https://nvd.nist.gov/vuln/detail/CVE-2026-45571
• https://github.com/advisories/GHSA-crhj-59gh-8x96

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

Details

Impact

Several denial-of-service issues were identified in go-git when parsing maliciously crafted Git repository data.

An attacker may craft a malicious .pack, .idx or loose objects that causes an application using an affected version of go-git to panic or consume excessive resources.

This can lead to denial of service in applications that use go-git to clone, fetch, open, or otherwise process untrusted repositories or Git object data.

Exploitation requires the ability to alter read-only files such as .pack or .idx from the local repository's .git/objects/pack/ directory. Alternatively, the user would need to be interacting with a malicious remote server, which is not recommended and exposes users to a broader class of security risks beyond this issue.

Patches

Users should upgrade to a patched version in order to mitigate this vulnerability. Versions prior to v5 are likely to be affected, users are recommended to upgrade to a supported go-git version.

Credits

go-git thanks @​kodareef5, @​AyushParkara and @​N0zoM1z0 for reporting this in four separate reports. 🙇

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/go-git/go-git/security/advisories/GHSA-w5pp-99ch-qj29
• https://github.com/advisories/GHSA-w5pp-99ch-qj29

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

Details

Impact

A symlink traversal issue in go-git could allow worktree operations to modify files outside the intended worktree path.

The worktreeFilesystem wrapper rejected dangerous path strings, including paths containing .git, parent-directory components, or control characters. However, it did not prevent filesystem operations from following symbolic links that were already present in the worktree.

As a result, a path that is safe when evaluated as a string could still resolve into the repository's Git metadata directory. For example, if s is a symbolic link to .git, writing to s/config would modify .git/config.

A symbolic link at the final path component could also be followed. For example, if s points directly to .git/config, opening s for writing with truncation could overwrite the repository configuration.

Exploitation requires an attacker to be able to introduce or control a symbolic link in the worktree and cause the application to perform a write through that path.

Applications using storage/memory for their Storer, or go-billy/memfs for their Worktree, are not affected by this vulnerability.

Patches

The issue has been addressed by making the worktree filesystem wrapper a symlink-safe boundary.

Worktree operations now reject paths where an existing symbolic link in any path component could cause the operation to escape the intended worktree location, including symbolic links at the final component.

Users of filesystem-backed worktrees should upgrade to a patched version.

Credits

Thanks to @​kodareef5 for reporting this issue and working with the go-git security team toward its resolution. 🥇
We would also like to thank @​HughLewis20, who independently reported the same issue while a fix was already in progress.

Severity

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

References

• https://github.com/go-git/go-git/security/advisories/GHSA-hc8v-wwc9-vgxm
• https://github.com/go-git/go-git/commit/008a78f2dd86f52544ddff8b8e8ddeecdf3f7aab
• https://github.com/go-git/go-git/commit/661d1c7f101d34e002a3cfcf8dbea5b7421d07ac
• https://github.com/go-git/go-git/releases/tag/v5.19.2
• https://github.com/go-git/go-git/releases/tag/v6.0.0-alpha.5
• https://github.com/advisories/GHSA-hc8v-wwc9-vgxm

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

Details

Impact

A path traversal issue in go-git could allow malicious reference names to access files outside the repository's intended reference storage.

Loose references are stored under .git/<reference-name>. The reference name was previously used as a path without verifying that the resolved path remained within the reference storage. A name such as refs/heads/../../config could therefore resolve to unrelated repository metadata such as .git/config or .git/HEAD.

A malicious Git server could advertise such a reference name. The name may also survive refspec mapping; for example, it could be mapped to refs/remotes/origin/../../config during a clone or fetch operation.

This vulnerability affects filesystem-backed repositories using the storage/filesystem package and its dotgit reference storage. Users relying exclusively on the in-memory storage implementation, storage/memory, are not affected, because reference names are not resolved as filesystem paths.

Exploitation requires an application using go-git with filesystem-backed storage to interact with a malicious Git server or otherwise process attacker-controlled reference names.

Patches

The issue has been addressed by validating reference names at the dotgit storage entry points and rejecting names whose resolved paths could escape the reference storage.

Users of filesystem-backed storage should upgrade to a patched version.

Workarounds

Applications that exclusively use storage/memory are not affected and do not require a workaround for this vulnerability.

For applications using filesystem-backed storage, avoid cloning from or fetching from untrusted Git servers until an upgrade is possible.

Applications that directly construct or process reference names may also validate them before passing them to filesystem-backed go-git storage. Application-level validation should only be considered a temporary mitigation and does not replace upgrading to a patched version.

References

• Fixes:
  • https://github.com/go-git/go-git/pull/2247
  • https://github.com/go-git/go-git/pull/2254

Credits

Thanks to @​Saku0512 for reporting this issue and @​Sahana2524 for proposing the initial fix. 🙇

Severity

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

References

• https://github.com/go-git/go-git/security/advisories/GHSA-qgq7-7hm3-q39j
• https://github.com/go-git/go-git/pull/2247
• https://github.com/go-git/go-git/pull/2254
• https://github.com/go-git/go-git/commit/4a0e66d555de5f9a30c31e2df64f445f42bd01e7
• https://github.com/go-git/go-git/commit/da9f7d8a0e98b475600177348d6ece384a370f36
• https://github.com/go-git/go-git/releases/tag/v5.19.2
• https://github.com/go-git/go-git/releases/tag/v6.0.0-alpha.5
• https://github.com/advisories/GHSA-qgq7-7hm3-q39j

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

v5.19.2

Compare Source

What's Changed

• build: Update module golang.org/x/crypto to v0.52.0 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​2150
• build: Update module github.com/go-git/go-git/v5 to v5.19.1 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​2141
• build: Update module golang.org/x/net to v0.55.0 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​2152
• git: Worktree: Add stores index entires with backslashes on Windows by @​joshblum in #​2262
• storage: dotgit, reject path traversal in reference names by @​pjbgf in #​2254
• build: Update module golang.org/x/net to v0.56.0 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​2267
• build: Update module golang.org/x/text to v0.39.0 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​2268
• [v5] git: worktree, make the filesystem wrapper a symlink-safe boundary by @​pjbgf in #​2277

Full Changelog: go-git/go-git@v5.19.1...v5.19.2

v5.19.1

Compare Source

What's Changed

• v5: plumbing: transport/ssh, Shell-quote path by @​hiddeco in #​2068
• v5: git: submodule, Fix relative URL resolution by @​hiddeco in #​2070
• v5: git: submodule, canonical remote for relative URLs by @​hiddeco in #​2074
• v5: git: submodule, error on remote without URLs by @​hiddeco in #​2078
• v5: plumbing: format/idxfile, Validate offset64 indices by @​hiddeco in #​2084
• v5: *: Reject malformed variable-length integers by @​hiddeco in #​2092
• v5: plumbing: format/packfile, Tighten delta validation by @​hiddeco in #​2091
• v5: Add worktreeFilesystem wrapper for worktree and hardening by @​hiddeco in #​2100
• v5: config: validate submodule names by @​hiddeco in #​2082
• build: Update module github.com/go-git/go-git/v5 to v5.19.0 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​2111
• v5: git: Allow MkdirAll on worktree-root paths by @​hiddeco in #​2117
• v5: git: Stop validating symlink target paths by @​pjbgf in #​2116
• v5: plumbing: format decoder input bounds and contracts by @​hiddeco in #​2125
• plumbing: format/packfile, cap delta chain depth in parser by @​pjbgf in #​2137

Full Changelog: go-git/go-git@v5.19.0...v5.19.1

v5.19.0

Compare Source

What's Changed

• build: Update module github.com/go-git/go-git/v5 to v5.18.0 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​2010
• v5: Bump sha1cd and go-billy by @​pjbgf in #​2060
• v5: Align object encoding with upstream by @​pjbgf in #​2065

Full Changelog: go-git/go-git@v5.18.0...v5.19.0

v5.18.0

Compare Source

What's Changed

• plumbing: transport/http, Add support for followRedirects policy by @​pjbgf in #​2004

Full Changelog: go-git/go-git@v5.17.2...v5.18.0

v5.17.2

Compare Source

What's Changed

• build: Update module github.com/go-git/go-git/v5 to v5.17.1 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1941
• dotgit: skip writing pack files that already exist on disk by @​pjbgf in #​1944

⚠️ This release fixes a bug (#​1942) that blocked some users from upgrading to v5.17.1. Thanks @​pskrbasu for reporting it. 🙇

Full Changelog: go-git/go-git@v5.17.1...v5.17.2

v5.17.1

Compare Source

What's Changed

• build: Update module github.com/cloudflare/circl to v1.6.3 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1930
• [v5] plumbing: format/index, Improve v4 entry name validation by @​pjbgf in #​1935
• [v5] plumbing: format/idxfile, Fix version and fanout checks by @​pjbgf in #​1937

Full Changelog: go-git/go-git@v5.17.0...v5.17.1

v5.17.0

Compare Source

What's Changed

• build: Update module github.com/go-git/go-git/v5 to v5.16.5 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1839
• git: worktree, optimize infiles function for very large repos by @​k-anshul in #​1853
• git: Add strict checks for supported extensions by @​pjbgf in #​1861
• backport, git: Improve Status() speed with new index.ModTime check by @​cedric-appdirect in #​1862
• storage: filesystem, Avoid overwriting loose obj files by @​pjbgf in #​1864

Full Changelog: go-git/go-git@v5.16.5...v5.17.0

v5.16.5

Compare Source

What's Changed

• build: Update module golang.org/x/crypto to v0.45.0 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1744
• build: Bump Go test versions to 1.23-1.25 (v5) by @​pjbgf in #​1746
• [v5] git: worktree, Don't delete local untracked files when resetting worktree by @​Ch00k in #​1800
• Expand packfile checks by @​pjbgf in #​1836

Full Changelog: go-git/go-git@v5.16.4...v5.16.5

v5.16.4

Compare Source

What's Changed

• backport plumbing: format/idxfile, prevent panic by @​swills in #​1732
• [backport] build: test, Fix build on Windows. by @​pjbgf in #​1734
• build: Update module golang.org/x/net to v0.38.0 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1742
• build: Update module github.com/cloudflare/circl to v1.6.1 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1741
• build: Update module github.com/go-git/go-git/v5 to v5.13.0 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1743

Full Changelog: go-git/go-git@v5.16.3...v5.16.4

v5.16.3

Compare Source

What's Changed

• internal: Expand regex to fix build [5.x] by @​baloo in #​1644
• build: raise timeouts for windows CI tests and disable CIFuzz [5.x] by @​baloo in #​1646
• plumbing: support commits extra headers, support jujutsu signed commit [5.x] by @​baloo in #​1633

Full Changelog: go-git/go-git@v5.16.2...v5.16.3

v5.16.2

Compare Source

What's Changed

• utils: fix diff so subpaths work for sparse checkouts, fixes 1455 to releases/v5.x by @​kane8n in #​1567

Full Changelog: go-git/go-git@v5.16.1...v5.16.2

v5.16.1

Compare Source

What's Changed

• utils: merkletrie, Fix diff on sparse-checkout index. Fixes #​1406 to releases/v5.x by @​kane8n in #​1561

New Contributors

• @​kane8n made their first contribution in #​1561

Full Changelog: go-git/go-git@v5.16.0...v5.16.1

v5.16.0

Compare Source

What's Changed

• [v5] plumbing: support mTLS for HTTPS protocol by @​hiddeco in #​1510
• v5: plumbing: transport, Reintroduce SetHostKeyCallback. Fix #​1514 by @​pjbgf in #​1515

Full Changelog: go-git/go-git@v5.15.0...v5.16.0

v5.15.0

Compare Source

What's Changed

• plumbing: add cert auth support to releases/v5.x by @​Javier-varez in #​1482
• v5: Bump dependencies by @​pjbgf in #​1505

Full Changelog: go-git/go-git@v5.14.0...v5.15.0

v5.14.0

Compare Source

What's Changed

• v5: Bump Go and dependencies to mitigate GO-2025-3487 by @​pjbgf in #​1436

⚠️ Note that this version requires Go 1.23, due to the bump to golang.org/x/crypto@v0.35.0 which mitigates the CVE above. User's that can't bump to Go 1.23 will need to remain on the previous v5.13.x release.

Full Changelog: go-git/go-git@v5.13.2...v5.14.0

v5.13.2

Compare Source

What's Changed

• plumbing: use the correct user agent string. Fixes #​883 by @​uragirii in #​1364
• build: bump golang.org/x/sys from 0.28.0 to 0.29.0 in the golang-org group by @​dependabot in #​1365
• build: bump the golang-org group with 2 updates by @​dependabot in #​1367
• build: bump github.com/ProtonMail/go-crypto from 1.1.3 to 1.1.4 by @​dependabot in #​1368
• build: bump github.com/go-git/go-billy/v5 from 5.6.1 to 5.6.2 by @​dependabot in #​1378
• build: bump github/codeql-action from 3.28.0 to 3.28.1 by @​dependabot in #​1376
• build: bump github.com/elazarl/goproxy from 1.2.3 to 1.4.0 by @​dependabot in #​1377
• git: worktree, fix restoring dot slash files (backported to v5). Fixes #​1176 by @​BeChris in #​1361
• build: bump github.com/pjbgf/sha1cd from 0.3.0 to 0.3.2 by @​dependabot in #​1392
• git: worktree_status, fix adding dot slash files to working tree (backported to v5). Fixes #​1150 by @​BeChris in #​1359
• build: bump github.com/ProtonMail/go-crypto from 1.1.4 to 1.1.5 by @​dependabot in #​1383

Full Changelog: go-git/go-git@v5.13.1...v5.13.2

v5.13.1

Compare Source

What's Changed

• build: bump github.com/go-git/go-billy/v5 from 5.6.0 to 5.6.1 by @​dependabot in #​1327
• build: bump github.com/elazarl/goproxy from 1.2.1 to 1.2.2 by @​dependabot in #​1329
• build: bump github.com/elazarl/goproxy from 1.2.2 to 1.2.3 by @​dependabot in #​1340
• Revert "plumbing: transport/ssh, Add support for SSH @​cert-authority." by @​pjbgf in #​1346

Full Changelog: go-git/go-git@v5.13.0...v5.13.1

v5.13.0

Compare Source

What's Changed

• build: bump github.com/go-git/go-git/v5 from 5.11.0 to 5.12.0 in /cli/go-git by @​dependabot in #​1065
• build: bump golang.org/x/net from 0.22.0 to 0.23.0 by @​dependabot in #​1068
• build: bump golang.org/x/net from 0.23.0 to 0.24.0 by @​dependabot in #​1071
• Properly support skipping of non-mandatory extensions by @​codablock in #​1066
• git: Refine some codes in test and non-test. by @​onee-only in #​1077
• plumbing: protocol/packp, client-side filter capability support by @​edigaryev in #​1000
• build: bump golang.org/x/net from 0.22.0 to 0.23.0 in /cli/go-git by @​dependabot in #​1078
• plumbing: fix sideband demux on flush by [@&#

✂ Note

PR body was truncated to here.