jcarr/git2go, branch v0.1.1

lame

2024-12-18T04:04:22Z

Signed-off-by: Jeff Carr

Merge branch 'devel'

2024-12-17T21:02:44Z

rename as libgit2

2024-12-17T21:01:59Z

better gitpb

2024-12-17T19:19:35Z

update to libgit2 version 1.8.4. dump old github and vendor stuff

2024-12-16T23:50:57Z

go install go.wit.com/apps/go-clone@latest go install go.wit.com/apps/go-mod-clean@latest go-clone --recusive go.wit.com/lib/git2go Signed-off-by: Jeff Carr

Replace golang.org/x/crypto/openpgp with github.com/ProtonMail/go-crypto

2022-12-09T20:43:11Z

The golang.org/x/crypto/openpgp library has been deprecated for over a year now (see golang.org/issue/44226, and the deprecation notice in the package documentation). The library is unmaintained and has a number of API and usability issues. ProtonMail maintains a community fork which is actively maintained, and for most cases is a drop-in replacement. This change switches usages of golang.org/x/crypto/openpgp/... with github.com/ProtonMail/go-crypto/openpgp/..., the only other code changes are adding a nil packet.Config to a openpgp.CheckArmoredDetachedSignature call. (This change is part of a wider effort by the Go Security team to remove usages of golang.org/x/crypto/openpgp from the Go ecosystem.)

Fix the `github-tag-action` workflow (#932)

2022-10-05T01:12:23Z

This has been failing for a while because of some changes in `git`.

libgit2 v1.5.0 #major (#929)

2022-10-04T14:50:57Z

Update libgit2 to v1.5.0. Replace `SmartProxyOptions()` with `SmartRemoteConnectOptions()`. Fixes: https://github.com/libgit2/git2go/issues/899 Signed-off-by: Sanskar Jaiswal Co-authored-by: lhchavez

Set BasicAuth in http.go only if username and password are not empty (#914)

2022-07-13T11:50:31Z

This prevents error "read/write on closed pipe". Go's http.client::send() always closes req.Body, so if the first request attempt is unsuccessful, any subsequent requests after calling the `CredentialsCallback` will attempt to read/write on a closed pipe.

Uprev libgit to v1.3.1 (#911)

2022-04-14T14:09:59Z

🔒 This is a security release to provide compatibility with git's changes to address [CVE 2022-24765](https://github.blog/2022-04-12-git-security-vulnerability-announced/). libgit2 (and by extension git2go) are not directly affected by this vulnerability, because libgit2 does not directly invoke any executable. 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. In this release, we will now validate that the user opening the repository is the same user that owns the on-disk repository. This is to match git's behavior. In addition, we are providing several correctness fixes where invalid input can lead to a crash. These may prevent possible denial of service attacks. At this time there are not known exploits to these issues.