-
Notifications
You must be signed in to change notification settings - Fork 2.6k
fix(cli): allow custom 403 error message #13443
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.
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
Merged
+46
−1
Conversation
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
🦋 Changeset detectedLatest commit: 08521ff The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
markandrus
approved these changes
Jun 13, 2025
chris-olszewski
approved these changes
Jun 13, 2025
Merged
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jun 16, 2025
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## vercel@43.2.0 ### Minor Changes - fix(cli): allow custom 403 error message ([#13443](#13443)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
zyankali83
approved these changes
Jun 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, the link command handles all 403 errors from the API with the same generic error message, except when the error contains "missingToken" or "invalidToken". This approach lacks specificity for various error conditions.
This PR modifies the error handling to only use the generic message when the error code is specifically "forbidden" or "team_unauthorized". All other 403 errors will now pass through their original API error messages. This change enables more precise error reporting to users, making troubleshooting more straightforward by exposing the actual underlying issues rather than masking them behind a generic message.