git2go/go.mod

module github.com/libgit2/git2go/v28

go 1.13

require (
	github.com/google/shlex v0.0.0-20191202100458-e7afc7fbc510
	golang.org/x/crypto v0.0.0-20201203163018-be400aefbc4c
	golang.org/x/sys v0.0.0-20201204225414-ed752295db88 // indirect
)
Add the /v28 suffix to go.mod This is compliant with https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher, which says ``` Major branch: Update the go.mod file to include a /v3 at the end of the module path in the module directive (e.g., module github.com/my/module/v3). Update import statements within the module to also use /v3 (e.g., import "github.com/my/module/v3/mypkg"). Tag the release with v3.0.0. ``` This also means that unfortunately we cannot keep using libgit2's exact version number (plus a build number for git2go purposes, since go only recognizes vMAJOR.MINOR.PATCH format). (Tentatively) fixes: #536 2020-02-18 21:21:38 -06:00			`module github.com/libgit2/git2go/v28`
Add the version number to go.mod This is the second take on trying to tag the current release with a Go version. (cherry picked from commit a32375a86063768507a01b32cc3d868f4c2ffa9c) 2020-03-19 09:45:38 -05:00
			`go 1.13`
Add `NewCredentialSSHKeyFromSigner` (#706) This change adds `NewCredentialSSHKeyFromSigner`, which allows idiomatic use of SSH keys from Go. This also lets us spin off an SSH server in the tests. (cherry picked from commit abf02bc7d79dfb7b0bbcd404ebecb202cff2a18e) 2020-12-06 13:55:04 -06:00
			`require (`
			`github.com/google/shlex v0.0.0-20191202100458-e7afc7fbc510`
			`golang.org/x/crypto v0.0.0-20201203163018-be400aefbc4c`
			`golang.org/x/sys v0.0.0-20201204225414-ed752295db88 // indirect`
			`)`