From c85834acbd81d2d51e4ccc8571d2ac28055c51eb Mon Sep 17 00:00:00 2001 From: Farnabaz Date: Fri, 23 Oct 2026 17:31:27 +0200 Subject: [PATCH] chore: drop redundant Vercel deploy from release workflow The Vercel GitHub integration already deploys `apps/website` from `main`, so the Vercel CLI production deploy in the release workflow is redundant. This removes the "Deploy to Vercel" step from `.github/workflows/release.yml`, along with the `deploy` input on `workflow_dispatch` that only existed to force it. `workflow_dispatch` itself stays, so a release can still be triggered by hand. The website build, tests, lint, and changesets publish steps are unchanged. So is `id-token: write`, which npm trusted publishing needs. --- .github/workflows/release.yml | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 9ca4a65b..d3f1f19e 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -5,11 +5,6 @@ on: branches: - main workflow_dispatch: - inputs: - deploy: - description: "Force Deploy to Vercel even if no packages were published" - type: boolean - default: true concurrency: ${{ github.workflow }}-${{ github.ref }} @@ -75,12 +70,3 @@ jobs: env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} NPM_TOKEN: "" # Workaround for https://github.com/changesets/action/pull/545 - - - name: Deploy to Vercel - if: >- - steps.changesets.outputs.published == 'true' || - (github.event_name == 'workflow_dispatch' && inputs.deploy) - run: npx vercel --prod --token=${{ secrets.VERCEL_TOKEN }} - env: - VERCEL_ORG_ID: ${{ secrets.VERCEL_ORG_ID }} - VERCEL_PROJECT_ID: ${{ secrets.VERCEL_PROJECT_ID }}