Skip to content

Update publisher CLI for BorderPulse-scoped token compatibility #109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sbc1-code merged 1 commit into from
Sep 30, 2026
Merged

Update publisher CLI for BorderPulse-scoped token compatibility #109

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/publish-vercel.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion docs/REFRESH-OPERATIONS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading