Closed aknysh closed 3 years ago
@aknysh Thanks for writing this up! This has been addressed in v0.36.1. Since that version, variant embeds the version number of itself, and use that to produce the go.mod
used internally to produce the binary.
The issue had also affected variant export go
, and the PR fixes that command as well.
Would you mind giving it a try with v0.36.1?
what
variant-export-binary
should use the same version of variantgo
packagewhy
variant export binary
generates a temporarygo
project that uses the latest variant package (e.g. 0.35.0) regardless of the version of variant command (e.g. 0.34.1), producing this error