From f7d6e765b62eaa91a014c5ac20fd6a3a4ed3e787 Mon Sep 17 00:00:00 2001 From: peptiderepo Date: Tue, 9 Jun 2026 06:23:30 +0000 Subject: [PATCH] =?UTF-8?q?ci:=20restore=20deploy=20pipeline=20=E2=80=94?= =?UTF-8?q?=20remove=20invalid=20continue-on-error=20on=20smoke=20job?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The smoke job is a reusable-workflow 'uses:' call; Actions does not support continue-on-error there, producing a 0-job workflow failure that has failed every deploy (so v0.5.0 never reached production). Matches the prautoblogger fix in #147. Smoke is not in deploy-production needs, so it stays non-blocking. Agent-Session: cto restore-prcore-deploy --- .github/workflows/deploy.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index abcdcb7..5d5a7dd 100755 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -51,7 +51,6 @@ jobs: smoke: name: Smoke tests (staging) needs: deploy-staging - continue-on-error: true uses: peptiderepo/peptide-e2e/.github/workflows/smoke.yml@main secrets: STAGING_WP_ADMIN_USER: ${{ secrets.STAGING_WP_ADMIN_USER }}