I should have called this out more prominently in #43, but didn't: each time we tag a release, we need to update this line in the Go wrapper to point to the release instead of "canary", which is only appropriate for the main branch.
The Go wrapper in the v0.3.0 release points to the "canary" release, whereas it should point to "v0.3.0" instead. I plan to do a v0.3.1 release to address this.
I should have called this out more prominently in #43, but didn't: each time we tag a release, we need to update this line in the Go wrapper to point to the release instead of "canary", which is only appropriate for the
mainbranch.The Go wrapper in the
v0.3.0release points to the "canary" release, whereas it should point to "v0.3.0" instead. I plan to do av0.3.1release to address this.