From 6598cf1d1c9ec04066d784984a0c782d23eb9787 Mon Sep 17 00:00:00 2001 From: David Pugh Date: Wed, 5 Aug 2026 19:02:00 +0100 Subject: [PATCH] ci: do not let SonarCloud block publishing A rejected SONAR_TOKEN failed the scan, which skipped publish-package and blocked the 0.1.1 release. --- .github/workflows/pipeline.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/pipeline.yaml b/.github/workflows/pipeline.yaml index bc2b0c8..e2aed53 100644 --- a/.github/workflows/pipeline.yaml +++ b/.github/workflows/pipeline.yaml @@ -193,6 +193,12 @@ jobs: sonarcloud: name: SonarCloud (${{ github.event_name }}) runs-on: ubuntu-latest + # A rejected SONAR_TOKEN made this job fail, which skipped publish-package + # (which needs it) and so blocked releases entirely. At job level this makes + # needs.sonarcloud.result report success so dependents run, while the job + # still shows a red X and the run still reports failure, so a broken scan + # stays visible rather than being silently swallowed. + continue-on-error: true needs: - changes if: >