Repository navigation
Update publisher CLI for BorderPulse-scoped token compatibility - #109
Merged
Merged
Conversation
1 of 10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The first approved production publication stopped before build because Vercel CLI 50.1.6 reads team resources while resolving a linked project; the BorderPulse-only token correctly denies team-level access. Pin the current official CLI 61.1.0 in GitHub Actions and align the operations instructions, preserving the project-only credential scope.
No application/runtime or DNS change. Verification: npm registry confirms version 61.1.0 supports Node >=20; the workflow runs Node 24. Existing release checks will run for this change, followed by an actual production publication to confirm authentication, packaging and upload. Failed publication run: https://github.com/sbc1-code/borderpulse/actions/runs/36672822869. Tracks #101 and #108.