From 9dabe8ccd232739614b21119bc63116567538653 Mon Sep 17 00:00:00 2001 From: Ning Sun Date: Thu, 10 Sep 2026 14:20:53 +0000 Subject: [PATCH] docs: fix README canary release badge resolving to stable version (#9109) The canary badge's filter (!*-*-*) only excludes tags with two or more dashes (nightly and dev builds), so zero-dash stable tags also pass. Because shields.io picks the newest release by date and v1.2.0 GA was created after v1.3.0-alpha.1, the canary badge displayed v1.2.0, which is already covered by the stable badge. Add sort=semver so shields picks the semver-greatest matching tag instead: v1.3.0-alpha.1 now ranks above v1.2.0. Also apply sort=semver to the stable badge to protect it from the same date-order failure when a patch of an older minor is released after a newer GA. Signed-off-by: Ning Sun --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e95f7849e4..1f5e740db9 100644 --- a/README.md +++ b/README.md @@ -20,10 +20,10 @@ One engine, on your infrastructure. -Stable +Stable -Canary +Canary Nightly