diff --git a/.github/badges/conformance.svg b/.github/badges/conformance.svg index f515344..c69ff6a 100644 --- a/.github/badges/conformance.svg +++ b/.github/badges/conformance.svg @@ -1,10 +1,10 @@ - - trsdn standard: v1.28.1 - Healthy + + trsdn standard: v1.28.2 - Healthy trsdn standard - v1.28.1 - Healthy + v1.28.2 - Healthy diff --git a/.github/conformance.yml b/.github/conformance.yml index 084cad2..8901226 100644 --- a/.github/conformance.yml +++ b/.github/conformance.yml @@ -6,7 +6,7 @@ # The badge in .github/badges/ is generated from this file. Change the evidence # first, then this record, then regenerate. Never the other way round. -standard_version: "1.28.1" +standard_version: "1.28.2" assessed_on: "2026-09-25" state: "Healthy" evidence: "docs/self-assessment.md" diff --git a/CHANGELOG.md b/CHANGELOG.md index f64850b..9a39fcd 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,16 @@ recorded here. Versions follow the compatibility policy in the [Repository Quality Standard](docs/repository-quality-standard.md). +## 1.28.2 - 2026-09-25 + +- `REC-02` now says to take the release assets as the authority for the count, + which was in the original proposal and was lost when it moved sections. +- [Status Badges](docs/repository-quality-standard.md#status-badges) points at + `REC-02`, so the badge is findable where a reader is already thinking about + badges rather than only in the recommendations table. +- Released as patch: a recommendation produces no result, and a cross-reference + changes none either. + ## 1.28.1 - 2026-09-25 - Added `REC-02`: a live total-download badge for repositories that publish diff --git a/docs/repository-quality-standard.md b/docs/repository-quality-standard.md index 00d9d40..3885f17 100644 --- a/docs/repository-quality-standard.md +++ b/docs/repository-quality-standard.md @@ -1,6 +1,6 @@ # Repository Quality Standard -- Version: 1.28.1 +- Version: 1.28.2 - Last reviewed: 2026-09-21 - Review cadence: every six months, even when nothing changes @@ -1762,6 +1762,11 @@ Rules: A hardcoded `Swift 5.9` badge beside a manifest that has moved to 6.0 is the failure this section exists to prevent. +A repository that publishes downloadable release assets may also show a live +total-download count. That badge is [`REC-02`](#recommendations) and not part of +the block this criterion requires, so it adds no condition to `P08` and its +absence is not a gap. + Badge hosting is not a privacy question on GitHub. Markdown rendered on `github.com` loads every external image through GitHub's proxy, so the image host observes the proxy and not the reader. The `Y02` argument applies where that @@ -2075,7 +2080,7 @@ which is how the same decision gets made differently in every repository. | | Recommendation | |---|---| | REC-01 | Name the performance-sensitive paths a change should be reviewed against, and how they are measured — a benchmark, a profiling routine, or a documented review pass. This was criterion `S14` until 1.28.0. It is worth doing and it is not worth assessing: whether a path is performance-sensitive is a judgement no fixed line decided consistently, so the criterion measured whether a sentence existed rather than whether the practice did. [A performance-review agent](../packages/performance-review/README.md) is one way to run such a review. | -| REC-02 | Where a repository publishes downloadable release assets, show a live total-download count and link it to the releases page: `[![Downloads](https://img.shields.io/github/downloads/OWNER/REPOSITORY/total?label=downloads)](https://github.com/OWNER/REPOSITORY/releases)`. It is not part of the badge block `P08` requires and adds no condition to it. GitHub counts asset downloads rather than unique users or installations, and checksum downloads are included in the total, so read it as a direction and not a figure. | +| REC-02 | Where a repository publishes downloadable release assets, show a live total-download count, taking the release assets as the authority and linking the badge to the releases page: `[![Downloads](https://img.shields.io/github/downloads/OWNER/REPOSITORY/total?label=downloads)](https://github.com/OWNER/REPOSITORY/releases)`. It is not part of the badge block `P08` requires and adds no condition to it. GitHub counts asset downloads rather than unique users or installations, and checksum downloads are included in the total, so read it as a direction and not a figure. | ## Changing This Standard diff --git a/docs/self-assessment.md b/docs/self-assessment.md index 00144f7..9b39ffe 100644 --- a/docs/self-assessment.md +++ b/docs/self-assessment.md @@ -1,6 +1,6 @@ # Self-Assessment: trsdn/.github -- Standard version: 1.28.1 +- Standard version: 1.28.2 - Assessed on: 2026-09-25 - State: **Healthy** - Record: [`.github/conformance.yml`](../.github/conformance.yml) diff --git a/standard.yml b/standard.yml index 71ce285..ce90e11 100644 --- a/standard.yml +++ b/standard.yml @@ -3,7 +3,7 @@ # Generated by scripts/standard.py from # docs/repository-quality-standard.md. Do not edit by hand. -version: "1.28.1" +version: "1.28.2" last_reviewed: "2026-09-21" prefixes: diff --git a/templates/conformance.yml b/templates/conformance.yml index fb028e6..a262bd3 100644 --- a/templates/conformance.yml +++ b/templates/conformance.yml @@ -20,7 +20,7 @@ # The badge is generated from this file. Change the evidence first, then this # record, then regenerate. Never the other way round. -standard_version: "1.28.1" +standard_version: "1.28.2" assessed_on: "YYYY-MM-DD" state: "Needs work" evidence: "docs/self-assessment.md"