From aca58872f3b8a8097a353ae876409e20047fad98 Mon Sep 17 00:00:00 2001 From: EtienneLescot Date: Mon, 24 Aug 2026 13:17:54 +0200 Subject: [PATCH] fix(ci): don't let the docs refresh block Microsoft Store publishing publish-msstore needs publish-release to succeed. The docs-refresh step lived in that same job with no continue-on-error, so its failure (unrelated to whether the release itself published) marked the whole job failed and silently skipped the Store submission via the needs graph. That's what happened to v1.10.0. --- .github/workflows/build.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index 4d6ecbfb..46be1ddd 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -988,6 +988,12 @@ jobs: # with a tag ref and failed its deploy every time. See docs.yml. if: ${{ steps.release.outputs.is_prerelease == 'false' }} timeout-minutes: 20 + # Bookkeeping, not publishing: the release itself is already out by the time + # this runs. Letting it fail the job silently skipped publish-msstore on + # v1.10.0 (an unrelated Store submission, gated on this job's `needs` success) + # even though "Publish release assets" above had already succeeded. Allowed + # to fail so a flaky docs deploy never blocks a downstream publish step. + continue-on-error: true env: GH_TOKEN: ${{ secrets.OPENSCREEN_RELEASE_TOKEN }} run: |