fix(release): treat launcher E403 as an ownership warning, not a failed release#21
Merged
Merged
Conversation
…ed release The npm token's account isn't on the unscoped 'synsci' package's owner list yet, so its publish 403s while every @synsci/* package ships fine. Downgrade exactly that case to a loud warning with the owner-grant fix spelled out; any other launcher error still fails the run.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 npm token's account is not yet on the unscoped
synscipackage's owner list, so its publish returns E403 while every@synsci/*package ships fine. With the strict failure handling this would turn every release red until the ownership grant happens.This downgrades exactly that case — E403/permission on the launcher — to a loud warning that spells out the fix (
npm owner add <token-user> synsci). Any other launcher failure still fails the run.Verified: turbo typecheck clean.