From e522fabff273997a1a4f8b8fa92bdb32f55c68a5 Mon Sep 17 00:00:00 2001 From: melbinjp Date: Tue, 18 Aug 2026 22:25:38 +0530 Subject: [PATCH] docs: pin the CI snippet at v0.1.3 v0.1.3 is out and carries both the rename-chain fix and the version fix, so the snippet people copy should get them. Done after the tag existed rather than in the release PR, so main never names a tag that is not there - which is the same class of broken-snippet defect this tool exists to find, and the README already shipped one once with 'pipx run docproof'. --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index e8a0718..7fb1485 100644 --- a/README.md +++ b/README.md @@ -62,7 +62,7 @@ clean bill of health nobody examined is worth less than nothing. - uses: actions/checkout@v4 with: fetch-depth: 0 # docproof needs history to tell drift from an example -- uses: melbinjp/docproof@v0.1.2 +- uses: melbinjp/docproof@v0.1.3 ``` **Both lines are load-bearing, and the action refuses to run without the first.** @@ -333,7 +333,7 @@ A gate that fails on day one gets removed on day one. `--exit-zero` prints the f leaves the run green, so you can adopt this while you are still working through them: ```yaml -- uses: melbinjp/docproof@v0.1.2 +- uses: melbinjp/docproof@v0.1.3 with: fail-on-findings: false ``` @@ -393,7 +393,7 @@ never existed, so `docproof` reports that and judges nothing rather than guessin - uses: actions/checkout@v4 with: fetch-depth: 0 # docproof needs history to tell drift from an example -- uses: melbinjp/docproof@v0.1.2 +- uses: melbinjp/docproof@v0.1.3 ``` **The action refuses to run without `fetch-depth: 0`, on purpose.** Measured on