Cannot get latest version: module contains a go.mod file, so module path should be github.com/buildkite/terminal-to-html/v3 about terminal-to-html HOT 5 CLOSED

I'm no golang expert, but I believe it's normal for there to be no binary after a go get command.

from terminal-to-html.

Hi @KateGo520, we’re aware of this and tracking it in #71.

If you’ve got the domain knowledge to spare, I’d love to know how we can test a multi-module project with dependency version updates such as this one - in #76 I’m attempting to fix the issue where the command-line version can’t import the parent dependency because there isn’t a published version yet, but we don’t want to publish a version without also bumping the command-line version. Is there a way to get go with go modules enabled to treat our working copy as the repo for the purposes of resolving the v3 module?

from terminal-to-html.

Apparently this is still an issue - I can reproduce it with go 1.15.

On master, go.mod no has the appropriate module suffix:

$ cat go.mod 
module github.com/buildkite/terminal-to-html/v3

go 1.12

require github.com/urfave/cli v1.22.4

However, the latest tagged release (3.3.0) still has an incorrect module path in go.mod:

https://github.com/buildkite/terminal-to-html/blob/v3.3.0/go.mod

Can we fix this for most users by tagged a 3.4.0 release with go.mod fixed up?

from terminal-to-html.

I've published a v.3.4.0 release, which I believe fixes this issue.

I haven't retrospectively changed the earlier 3.x releases that are unusable when go modules are enabled - mutating the tags felt icky and ultimately not really necessary.

Thanks for your patience!

from terminal-to-html.

@yob

I bumped into this, and ran

❯ go get github.com/buildkite/terminal-to-html/v3
go: downloading github.com/buildkite/terminal-to-html/v3 v3.6.1

Which is dumped into ls ~/go/pkg/mod/github.com/buildkite/terminal-to-html/[email protected]/ but doesn't seem to include a binary? Is that normal?

from terminal-to-html.