Repository navigation
feat(deploy-vercel): support project-scoped Vercel tokens - #17
Merged
Merged
Conversation
Port of aragon/app#1498: detect the token scope once, drop --scope for project tokens and take the REST fallbacks for pull and alias.
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
2 participants
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.
Port of aragon/app#1498 into the reusable deploy. Project-scoped tokens cannot resolve `--scope`, `vercel pull` or `vercel alias`; the token scope is detected once per job (`/v2/user`), classic and team tokens keep the CLI path, project tokens skip `--scope` and use the project-level REST endpoints for pull and alias. Without this, aragon/app#1486 would regress the fix that landed on `main` today.
🤖 Generated with Claude Code