Closed akihiro closed 1 year ago
Hi @akihiro thanks for reporting this. I bumped the version to v2.0.0 so that users would get a heads up on a recent breaking change, but I didn't realise this would break go install. In hindsight I probably should've kept it at v1, since the concept of semantic versions on Go modules really seems to be more about updating libraries.
I think the fix here is to change the package path in go.mod to include /v2
and update the installation instructions accordingly.
According to README.md, install using Go will fail.
but install alpaca v1.3.2 is well.