Yer replace is mentioned in the link I provided too and I’d seen that
thread, but as you can see from the amount of effort required I would
suggest that it’s currently not practical to have everyone go through that
process; particularly for tools when they just want to install and use not
develop
Hello Steve,
> https://golang.org/doc/go1.13#version-validation lists a number of
> options if you're maintaining a module but nothing seems relevant for
> CI/CD pipelines which are just trying to use tools for which they aren't
> the maintainer.
Regarding how to fix "invalid pseudo-version"
