docs: recommend the @v1 release tag for reusable-workflow consumers

The example stub + README pinned guidance pointed at @main/@<sha>; update them to recommend @v1 — gadfly's curated release tag that's moved on deliberate releases so central swarm tuning propagates without per-consumer re-pinning (full @<sha> still offered for an immutable pin; @main discouraged). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 00:10:01 -04:00
parent 0d80ae73d8
commit 6f85b9341f
2 changed files with 11 additions and 8 deletions
@@ -312,8 +312,10 @@ examples/              the ~15-line stub a consuming repo drops in

 The image is published to `gitea.stevedudenhoeffer.com/steve/gadfly`. Every push to `main`
 rebuilds and republishes `:latest` (plus `:sha-<short>`); pushing a `v*` tag publishes that
-pinned version (plus `:latest`). Pin consumers to a `:vN` tag for stability, or track
-`:latest` to ride main.
+pinned version (plus `:latest`). Pin full-stub consumers to a `:vN` image tag for stability, or track
+`:latest` to ride main. Reusable-workflow consumers likewise pin the workflow ref —
+`review-reusable.yml@v1` (a curated tag moved on releases, so central swarm tuning propagates) or
+a full `@<sha>` for an immutable pin; avoid `@main`.

 ## Configuration (advanced)