fix: allow go forge to install SHA versions when no tagged versions present

[Ajpantuso]

Summary

Fixes #1667

Makes it possible to install a go module from SHA when no tagged versions are available.

[endigma]

You should add a unit test for this so when there's a better solution (I hope there will be in the future) it's more clear that it works properly.

[Ajpantuso]

You should add a unit test for this so when there's a better solution (I hope there will be in the future) it's more clear that it works properly.

I'm not opposed to adding a test, but I don't think a unit will really capture the intended behavior unless there's an opportunity to mock out some of the go list ... output.

That points me to adding an e2e test, but we'd need to setup an external repo that mocks out this scenario.

So yes I think it makes sense to test this, but think it will add maintenance burden so will wait for input from maintainers.

[Ajpantuso]

Actually github.com/jdx/go-example is already used in the test suite so let me add something to e2e.

[endigma]

I meant e2e, unit doesn't work here really. jdx/go-example may not always reproduce the issue, it should be a perpetually tagless module, unless @jdx guarantees that.

[Ajpantuso]

I meant e2e, unit doesn't make sense here really. jdx/go-example may not always make sense here, it should be a perpetually tagless module, unless @jdx guarantees that.

Yeah hence the maintenance burden. Probably makes sense to make a public archive out of whatever repo is used.