From 9337abcca25ec01c39a373af9a5ccd108ad9341e Mon Sep 17 00:00:00 2001 From: kkdev92 Date: Wed, 2 Sep 2026 20:49:20 +0900 Subject: [PATCH] docs: show the release as a badge instead of naming it in prose The status line said `0.1.0`. That is correct today and wrong the day the next release is tagged, and nothing fails in between -- the reader is the one who finds out. Unlike the other repositories here, this one had no version badge to fall back on: it is firmware rather than a published package, so removing the number would have removed the information. A release badge replaces it. It reads from the repository's own releases, so it cannot disagree with them. Verified: the badge resolves and renders `v0.1.0`, which is the current tag. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_013Tfbt5Vy1jB9C6mMAHXhLY --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 0a6d04c..f9c5f99 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,6 @@ # stackchan-atoms3r +[![Release](https://img.shields.io/github/v/release/kkdev92/stackchan-atoms3r)](https://github.com/kkdev92/stackchan-atoms3r/releases) [![CI](https://github.com/kkdev92/stackchan-atoms3r/actions/workflows/ci.yml/badge.svg)](https://github.com/kkdev92/stackchan-atoms3r/actions/workflows/ci.yml) [![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/kkdev92/stackchan-atoms3r/badge)](https://scorecard.dev/viewer/?uri=github.com/kkdev92/stackchan-atoms3r) [![OpenSSF Best Practices](https://www.bestpractices.dev/projects/14114/badge)](https://www.bestpractices.dev/projects/14114) @@ -17,7 +18,7 @@ telemetry service. Project page: -> **Status:** 0.1.0 (best-effort maintenance) +> **Status:** Active (best-effort maintenance) ---