From 88cbb79d60c701b9967c3cef6ef37f698c070b39 Mon Sep 17 00:00:00 2001
From: sbc1-code <207095575+sbc1-code@users.noreply.github.com>
Date: Tue, 29 Sep 2026 22:30:34 -0700
Subject: [PATCH] fix: use current Vercel CLI for project-scoped deployment
 token

---
 .github/workflows/publish-vercel.yml | 2 +-
 docs/REFRESH-OPERATIONS.md           | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/publish-vercel.yml b/.github/workflows/publish-vercel.yml
index 85a63b3fa..16b2394c8 100644
--- a/.github/workflows/publish-vercel.yml
+++ b/.github/workflows/publish-vercel.yml
@@ -55,7 +55,7 @@ jobs:
           case "$PUBLISH_TARGET" in preview|production) ;; *) echo 'Invalid publication target'; exit 1;; esac
       - run: npm ci
       - name: Install pinned deployment CLI
-        run: npm install --global vercel@50.1.6
+        run: npm install --global vercel@61.1.0
       - name: Validate collector output and record provenance
         run: npm run publish:validate -- --write-manifest
       - name: Pull matching environment settings
diff --git a/docs/REFRESH-OPERATIONS.md b/docs/REFRESH-OPERATIONS.md
index 9db34daed..aa8e6cf73 100644
--- a/docs/REFRESH-OPERATIONS.md
+++ b/docs/REFRESH-OPERATIONS.md
@@ -120,7 +120,7 @@ Pages deployer. Both hosts build the same Vite app; only Vercel enables
    it snapshots latest `main` at job start to avoid queued pushes publishing
    older data. Its concurrency group serializes deployments.
 3. Dispatch `publish-vercel.yml`. It uses Node 24 and the existing Vercel CLI
-   version 50.1.6, validates inputs, pulls preview settings, runs `vercel build`
+   version 61.1.0, validates inputs, pulls preview settings, runs `vercel build`
    in Actions, runs `npm test`, rechecks freshness, and uploads with
    `vercel deploy --prebuilt`. It performs no remote Vercel build.
 4. Read the deployed `/data/publication.json` and compare it with the Actions