fix(browser): restore npm publishability lost in the #69 merge - #70
Merged
Conversation
The #69 branch forked before b89979e (publish agent-id-browser to npm) and its conflict resolution took the branch side of package.json wholesale — reintroducing "private": true and dropping publishConfig and the files whitelist. detect.shouldPublish therefore stayed false and 7.5.1 never reached the npm-publish gate.
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.
#69's branch forked before b89979e (publish agent-id-browser to npm), and its package.json conflict resolution took the branch side wholesale — reintroducing
"private": trueand droppingpublishConfig+ thefileswhitelist.detect.shouldPublishtherefore stayedfalseand 7.5.1 never reached the npm-publish gate. Restores the three fields; version stays 7.5.1.🤖 Generated with Claude Code