You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This attempts to simplify and tidy-up the logic for image labelling.
We would like the following behaviour:
- A build on `master` updates the `unstable` tag
- A build on a tag updates the `tag` tag, and also sets it to `latest`
if it has decided it's the latest tag.
The caveat above is that if we have released _0.23.0_ and then choose to
release _0.22.100_`, we don't want _0.22.100_ to become the `latest`
release. Only the "next" version.
Consider:
```sh
> cat a.txt
0.22.100
0.23.00
0.22.1
> sort -V a.txt
0.22.1
0.22.100
0.23.00
```
Fixes#2224
---
<!-- Consider each and tick it off one way or the other -->
* [x] CHANGELOG updated or not needed
* [x] Documentation updated or not needed
* [x] Haddocks updated or not needed
* [x] No new TODOs introduced or explained herafter
0 commit comments