activity/go.mod

module gitler.moe/suwako/activity

go 1.22

require (
	github.com/dave/jennifer v1.3.0
	github.com/go-test/deep v1.0.1
	github.com/golang/mock v1.2.0
	gitler.moe/suwako/httpsig v1.1.0
)

require (
	golang.org/x/crypto v0.17.0 // indirect
	golang.org/x/sys v0.15.0 // indirect
)
フォーク 2024-04-02 11:20:38 +09:00			`module gitler.moe/suwako/activity`
Update module files BUT enabling modules breaks the build. The new updates to golang modules ensure that this code generation solution just got a lot more painful, as now each generated subpackage needs its own go-mod file autogenerated, it seems. 2019-03-01 07:11:10 +09:00
. 2024-04-02 10:18:40 +09:00			`go 1.22`
Add go.mod and go.modverify for vgo 2018-05-31 04:44:17 +09:00
			`require (`
Update module files BUT enabling modules breaks the build. The new updates to golang modules ensure that this code generation solution just got a lot more painful, as now each generated subpackage needs its own go-mod file autogenerated, it seems. 2019-03-01 07:11:10 +09:00			`github.com/dave/jennifer v1.3.0`
Add go.mod and go.modverify for vgo 2018-05-31 04:44:17 +09:00			`github.com/go-test/deep v1.0.1`
Update module files BUT enabling modules breaks the build. The new updates to golang modules ensure that this code generation solution just got a lot more painful, as now each generated subpackage needs its own go-mod file autogenerated, it seems. 2019-03-01 07:11:10 +09:00			`github.com/golang/mock v1.2.0`
. 2024-04-02 11:23:03 +09:00			`gitler.moe/suwako/httpsig v1.1.0`
Add go.mod and go.modverify for vgo 2018-05-31 04:44:17 +09:00			`)`
. 2024-04-02 10:18:40 +09:00
			`require (`
			`golang.org/x/crypto v0.17.0 // indirect`
			`golang.org/x/sys v0.15.0 // indirect`
			`)`