On Sunday, September 15, 2019 at 12:35:27 PM UTC-4, Axel Wagner wrote:
>
> On Sun, Sep 15, 2019 at 6:11 PM T L >
> wrote:
>
>> Do you mean if there is already a require line in the go.mod file,
>> which requires a non-formal tagged version,
>> then "go get ...@latest" will rollback the require t
On Sun, Sep 15, 2019 at 6:11 PM T L wrote:
> Do you mean if there is already a require line in the go.mod file,
> which requires a non-formal tagged version,
> then "go get ...@latest" will rollback the require to the latest formal
> tagged version,
> but "go get ...@upgrade" will not?
>
AIUI (n
On Saturday, September 14, 2019 at 11:04:06 AM UTC-4, Axel Wagner wrote:
>
> Can you explain more specifically what you don't understand?
> The example seems pretty clear: Say you currently require the latest
> master commit (e.g. by using a pseudo-version), which is a couple commits
> ahead of
Can you explain more specifically what you don't understand?
The example seems pretty clear: Say you currently require the latest master
commit (e.g. by using a pseudo-version), which is a couple commits ahead of
the latest released version, then "latest" will select the release, while
"upgrade" wi
The doc https://golang.org/cmd/go/#hdr-Module_queries says:
The string "upgrade" is like "latest", but if the module is currently
> required at a later version than the version "latest" would select (for
> example, a newer pre-release version), "upgrade" will select the later
> version instead.
