Can we have tags with a 0 patch number for future releases?

I just ran into issues because I had been using tag 5.2-bionic, and the release of 5.2.3 broke a GitHub workflow. Next time there is a 0 patch, can we have a specific tag to reference it in a stable manner? i.e. 5.2.0-bionic

(Don’t worry. There is nothing actually wrong with 5.2.3. Some tooling was checking that a version it knew about was available before trying to use it, and it rejected 5.2.3 as unfamiliar.)

2 Likes

CC @mishal_shah / @tomerd

I think this is a good idea. @mishal_shah?

Sounds good, we will start doing this for future releases.

3 Likes