From 8a4e4b3549ebdd26259de17efdc53242d44151aa Mon Sep 17 00:00:00 2001
From: Richard <2470404+rmachielse@users.noreply.github.com>
Date: Fri, 21 Aug 2026 11:08:39 +0200
Subject: [PATCH] fix(ci): pin ruby-versions-action to v2.0.0

Build-Test-Push has failed every run since 2026-07-13, so the last
published image is the 2026-07-09 build and no Ruby release has
reached the registry since. The pinned v1.2.3 pulls
ruby-version-checker unpinned, and that binary now requires a
subcommand, so the action prints its usage text and returns empty
versions and metadata. The matrix expands to nothing, build-test-push
never runs, and merge-manifests is skipped.

v1.2.4 was the conservative choice, but its digest-pinned checker
predates Ruby 4.0 and still lists EOL 3.1. v2.0.0 reports 3.2 through
4.0 and is what upstream runs green weekly. It pulls the checker as
:latest, so the same class of break can recur, which is survivable
only if a failing scheduled run is noticed.

SWE-510
---
 .github/workflows/build-push.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/build-push.yaml b/.github/workflows/build-push.yaml
index e539537..7a38767 100644
--- a/.github/workflows/build-push.yaml
+++ b/.github/workflows/build-push.yaml
@@ -20,7 +20,7 @@ jobs:
       versions: ${{ steps.ruby-versions.outputs.versions }}
       metadata: ${{ steps.ruby-versions.outputs.metadata }}
     steps:
-      - uses: moritzheiber/ruby-versions-action@aa578bff78ea03e003a9a0d6fea9513b77be7cd0 # v1
+      - uses: moritzheiber/ruby-versions-action@456bdaf86444ac96b227a6e9f31c8cab76c7525e # v2.0.0
         name: Fetch latest Ruby versions
         id: ruby-versions