meilisearch/MeiliSearch
`latest` tag update: do it only if the GitHub release is considered as the latest one
オープン
#3,177 opened on 2022/12/01
bugcontribution acceptedgithub actionshelp wantedmaintenanceOLD
Repository metrics
- Stars
- (57,572 個のスター)
- PR merge metrics
- (平均マージ 11d 20h) (30d で 41 merged PRs)
説明
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.