From 3f585e32492d4591c4f7d2bf808423b6c3df81e4 Mon Sep 17 00:00:00 2001
From: Ildar Nurislamov <ildar@jitsu.com>
Date: Wed, 26 Aug 2026 18:19:54 +0400
Subject: [PATCH] fix(release): drop the moving `current` tag; consumers pin
 release tags

Reverts the `current` half of #10 (the gpt-5.6-terra switch stays).
release.yml no longer force-moves a `current` tag; README documents pinning
a dated release tag (currently 1.32.20260826) and bumping deliberately.
The `current` tag itself is deleted from origin once every consumer PR
references 1.32.20260826.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---
 .github/workflows/release.yml | 15 +--------------
 README.md                     | 18 ++++--------------
 2 files changed, 5 insertions(+), 28 deletions(-)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 9e4f4aa..b0cb552 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -28,18 +28,5 @@ jobs:
           echo "tag=$TAG" >> "$GITHUB_OUTPUT"
           echo "Created tag: $TAG"
 
-      # `current` is a moving tag that always points at the latest release on
-      # main. Consumers reference `ai-review.yml@current` so they pick up new
-      # releases without a per-repo re-pin. To roll back every consumer at
-      # once, move the tag by hand to an older release:
-      #   git tag -f current 1.30.20260821 && git push -f origin current
-      # (the next merge to main moves it forward again).
-      - name: "🏷️ Move `current` tag"
-        run: |
-          set -euo pipefail
-          git tag -f current
-          git push -f origin current
-          echo "Moved tag: current -> $(git rev-parse --short HEAD)"
-
       - name: "📝 Write summary"
-        run: echo "Released tag \`${{ steps.tag.outputs.tag }}\` (\`current\` now points here)" >> "$GITHUB_STEP_SUMMARY"
+        run: echo "Released tag \`${{ steps.tag.outputs.tag }}\`" >> "$GITHUB_STEP_SUMMARY"
diff --git a/README.md b/README.md
index 3e72114..c23f2ac 100644
--- a/README.md
+++ b/README.md
@@ -63,7 +63,7 @@ on:
 
 jobs:
   ai-review:
-    uses: jitsucom/github-workflows/.github/workflows/ai-review.yml@current
+    uses: jitsucom/github-workflows/.github/workflows/ai-review.yml@1.32.20260826
     secrets: inherit
     with:
       pr_number: ${{ inputs.pr_number }}
@@ -84,19 +84,9 @@ Use the `review_instructions` input to focus the review on what matters for your
 #### Versioning
 
 Every merge to `main` is tagged `1.<commit-count>.<yyyymmdd>` by
-[`release.yml`](.github/workflows/release.yml), which also moves the `current` tag to the
-same commit.
-
-- `@current` (recommended) — consuming repos pick up each release automatically on the
-  next run; no per-repo re-pin.
-- `@1.30.20260821` — pin a specific release if a repo needs to opt out of updates.
-
-To roll back **all** `@current` consumers at once, move the tag to an older release
-(the next merge to `main` moves it forward again):
-
-```sh
-git tag -f current 1.30.20260821 && git push -f origin current
-```
+[`release.yml`](.github/workflows/release.yml). Consuming repos pin a release tag and bump
+it deliberately — there is no floating tag, so a github-workflows release never changes a
+consumer's review behaviour until that repo opts in.
 
 ## Composite actions