From f4fa816ac763e3d9e163f2c9005dd56e8ad68c0d Mon Sep 17 00:00:00 2001
From: Jaro-c <75870284+Jaro-c@users.noreply.github.com>
Date: Mon, 27 Jul 2026 21:21:38 -0500
Subject: [PATCH] ci: label the freshness pin with its release
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The pin already pointed at the commit that became v1.11.0 — it was pinned
to the merge of Glyndor/.github#105 while the reusable was still waiting
for a consumer to prove it green, which this repository then did.

The SHA is what makes the pin safe; the version comment beside it is what
makes it visible. Without one Dependabot has no version to compare
against, so it never proposes a bump and the pin quietly rots. That is the
difference between a reusable this repository happens to call and one the
organisation can adopt.

Signed-off-by: Jaro-c <75870284+Jaro-c@users.noreply.github.com>
---
 .github/workflows/schedule-freshness.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/schedule-freshness.yml b/.github/workflows/schedule-freshness.yml
index 7b6e79d..734e2ed 100644
--- a/.github/workflows/schedule-freshness.yml
+++ b/.github/workflows/schedule-freshness.yml
@@ -25,14 +25,14 @@ permissions:
 jobs:
   audit:
     name: audit freshness
-    uses: Glyndor/.github/.github/workflows/schedule-freshness.yml@41d31f18d3ed3bb1a8cbbc44c68030e4867488b2
+    uses: Glyndor/.github/.github/workflows/schedule-freshness.yml@41d31f18d3ed3bb1a8cbbc44c68030e4867488b2 # v1.11.0
     with:
       workflow: audit.yml
       max-age-days: 15 # weekly cron, so two periods of slack
 
   fuzz:
     name: fuzz freshness
-    uses: Glyndor/.github/.github/workflows/schedule-freshness.yml@41d31f18d3ed3bb1a8cbbc44c68030e4867488b2
+    uses: Glyndor/.github/.github/workflows/schedule-freshness.yml@41d31f18d3ed3bb1a8cbbc44c68030e4867488b2 # v1.11.0
     with:
       workflow: fuzz.yml
       max-age-days: 15 # weekly cron, so two periods of slack