From 7037dcd865c9c347b121bf57fa7218533d2b8093 Mon Sep 17 00:00:00 2001 From: nicholasSUSE Date: Thu, 19 Nov 2026 18:11:20 -0300 Subject: [PATCH] ci: use the chart-owners branch of the charts action This workflow called the ship action of rancher/charts at a fixed commit. That commit is from before the check that every image of the chart is in the staging registry before the chart is pushed, so releases from this repository did not run it. The call now uses the chart-owners branch, which carries the checks, and a comment above it asks to keep it there and not to pin a commit. --- .github/workflows/stage-chart.yaml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/stage-chart.yaml b/.github/workflows/stage-chart.yaml index 14404d5d..2d8be587 100644 --- a/.github/workflows/stage-chart.yaml +++ b/.github/workflows/stage-chart.yaml @@ -42,7 +42,11 @@ jobs: run: ./.github/workflows/scripts/prepare-charts.sh "$TAG" "$RUNNER_TEMP/charts" - name: Stage the charts and notify rancher/charts - uses: rancher/charts/.github/actions/ship-family-staged@5b6d8660b09f1eeef144c56d455d191e67ac405a # chart-owners + # Please keep this action on the chart-owners branch and do not pin it to a commit. + # The branch carries the checks that stop a faulty release, for example that the + # images of the chart are pushed before the chart. A commit keeps only the checks + # that existed when it was copied. + uses: rancher/charts/.github/actions/ship-family-staged@chart-owners with: family: rancher-eks-operator chart-dirs: |