Oddity with v0.xxx tags

[Brian Candler]

I have just noticed a load of tags in the prometheus repo for v0.XXX (from v0.35.0 to v0.54.0 inclusiveq) which match with v2.XXX

For example:

https://github.com/prometheus/prometheus/tree/v0.54.0

https://github.com/prometheus/prometheus/releases/v0.54.0

and which github claims was only tagged last week, matches

https://github.com/prometheus/prometheus/tree/v2.54.0

(both are commit 5354e87a)

Is this perhaps to do with Go module versioning, or is something else going on here?

Thanks,

Brian.

[Ben Kochie]

Yes, this is a workaround for Go major versioning changes.

See: https://github.com/prometheus/prometheus/pull/12900

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/2a8e9ee0-252f-4049-b306-7d0865419842n%40googlegroups.com.

[Bjoern Rabenstein]

On 20.08.24 06:35, Ben Kochie wrote:
> Yes, this is a workaround for Go major versioning changes.
>
> See: https://github.com/prometheus/prometheus/pull/12900

Also,
https://github.com/prometheus/prometheus/blob/main/RELEASE.md#2-draft-the-new-release
has some explanation about it.

Note that v3 is imminent. For Go modules, v3.xx.y will be tagged as
0.3xx.y, e.g.

- 3.0.0 → 0.300.0
- 3.0.1 → 0.300.1
- 3.21.0 → 0.321.0

--
Björn Rabenstein
[PGP-ID] 0x851C3DA17D748D03
[email] bjo...@rabenste.in

[Ben Kochie]

That tagging scheme makes me sad.