chore(packages): set publishConfig.access=public on scoped packages#4
Merged
Conversation
Scoped npm packages default to private; without this, the first publish requires the changesets action to pass --access public, which it does not. Setting publishConfig at the package level is the durable fix. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
"publishConfig": { "access": "public" }to the three@flint/*scoped packages (adapter-anthropic,adapter-openai-compat,graph).restricted).Test plan
pnpm exec biome checkpasses on the modified filesNPM_TOKENis rotated to a granular token with 2FA bypass, Publish workflow succeeds end-to-end🤖 Generated with Claude Code