Aaah ok, so my usage should have been v1.0.0-pre-release.1 and
v1.0.0-pre-release.2 ; and indeed,
when I've tested it it does work.
Thank you
On Wednesday, April 29, 2020 at 8:41:39 PM UTC, Sean Liao wrote:
>
> semver point 10:
> > Build metadata MUST be ignored when determining version preceden
semver point 10:
> Build metadata MUST be ignored when determining version precedence.
chat log from slack:
> 22:29 bcmills Tags with metadata are not unique: there is only a partial
order among them, not a total order.
> 22:30 In contrast, MVS requires a total order. (We can't choose between
v
go does mean semver.org when it refers to semver
> Modules must be semantically versioned according to semver[,...]
refers to what the numbers mean, the v prefix is required but not part of
the version, more clearly explained in a faq on semver.org:
> Is “v1.2.3” a semantic version?
> No, “v1.2
On Wednesday, April 29, 2020 at 6:57:55 PM UTC, Uli Kunitz wrote:
>
> The documentation provided by go help modules doesn't refer to semver.org
> and the Backus-Naur-Form there, so you cannot assume it is supported. The
> semver.org BNF doesn't support the leading v letter, so Go modules
> ver
On Wednesday, April 29, 2020 at 6:57:55 PM UTC, Uli Kunitz wrote:
>
> The documentation provided by go help modules doesn't refer to semver.org
> and the Backus-Naur-Form there, so you cannot assume it is supported. The
> semver.org BNF doesn't support the leading v letter, so Go modules
> ver
The documentation provided by go help modules doesn't refer to semver.org
and the Backus-Naur-Form there, so you cannot assume it is supported. The
semver.org BNF doesn't support the leading v letter, so Go modules versions
are anyway incompatible.
--
You received this message because you are
