libgit2 users: I screwed up a change in the commit APIs for v1.8.1. We reverted the change in v1.8.2rc, and I'm trying to figure out the best path forward. If you have input, weigh in here: github.com/libgit2/libgit…
libgit2 is releasing security releases v1.6.5 and v1.7.2. We encourage our users to update to these latest security releases. github.com/libgit2/libgit…
libgit2 v1.6.0 (Hubbeliges Krokodil) is now available with experimental SHA256 support for bare repositories, partial stash, support for push-by-OID, and many bug fixes. github.com/libgit2/libgit…
libgit2 has released v1.4.5 and v1.5.1 to mitigate CVE 2023-22742. Prior versions did not validate remote ssh host keys by default, and required users to provide a callback. libgit2 now validates remote host keys. Users are encouraged to upgrade. github.com/libgit2/libgit…
Announcing libgit2 v1.5.0 with an experimental CLI for testing, refactoring for SHA256 support, a benchmarking tool, and numerous new features and bugfixes. github.com/libgit2/libgit…
We've released libgit2 v1.4.4 (and libgit2 v1.3.2) with security fixes to match git's CVE 2022-29187. We encourage all users to upgrade. github.com/libgit2/libgit…
libgit2 is not directly affected by this security issue (since libgit2 never directly executes other applications) but we are providing these changes as a security release for any users that use libgit2 for repository discovery and then also use git on that repository.