meilisearch/MeiliSearch
`latest` tag update: do it only if the GitHub release is considered as the latest one
Aberta
#3.177 aberto em 1 de dez. de 2022
bugcontribution acceptedgithub actionshelp wantedmaintenanceOLD
Métricas do repositório
- Stars
- (57.572 estrelas)
- Métricas de merge de PR
- (Métricas PR pendentes)
Description
Currently our current CI (to move the latest tag to the appropriate commit) will push the latest tag to the latest release in term of times and not in term of version.
For example:
- we release v1.10.0 ->
latesttag will correspond to thev1.10.0tag - then, later, we release v1.1.12 ->
latesttag will now correspond to thev1.1.12tag despite this is not the latest release,v1.10.0is!
We need to run the CI only if the release is considered as the latest one by GitHub.
The latest release is defined this way on GitHub when creating a new GitHub release.