From 2f80bfdef59e6edad06a95a821270c4595c3159f Mon Sep 17 00:00:00 2001 From: Marvin Zhang Date: Wed, 20 May 2026 13:40:39 +0800 Subject: [PATCH] ci: make publish validate-specs step non-fatal (#254) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The publish workflow's `Validate specs` step runs `node bin/leanspec.js validate --warnings-only`, but the Rust CLI's `validate` command is not yet migrated to the adapter API and exits non-zero before the `--warnings-only` flag takes effect. That blocks every release. Treat the step as advisory (`continue-on-error: true`) so the workflow can proceed to publish. The flag name already signals the intent. Remove the override once `validate` is migrated. Part of #254 — unblocks the `leanspec@0.3.0` publish (run 26143212968). Co-Authored-By: Claude Opus 4.7 (1M context) --- .github/workflows/publish.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index f4c398d69..88e19b370 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -368,6 +368,7 @@ jobs: - name: Validate specs if: ${{ github.event_name != 'workflow_dispatch' || !inputs.dry_run }} + continue-on-error: true run: node bin/leanspec.js validate --warnings-only - name: Prepare packages for npm publish