build: drop private:true now that publishing is intentional - #35
Merged
jonathanKingston merged 1 commit intoJul 5, 2026
Merged
Conversation
The package is now deliberately published to public npm via trusted publishing, so the private:true guard is obsolete friction: it forced the release workflow to strip it at publish time and left the committed manifest out of sync with what ships. Remove the field and the corresponding `npm pkg delete private` step; publishConfig.access=public plus authenticated/OIDC publishing already control who can publish. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GybqjwKSadmFZv4cxE5Y5N
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.
Follow-up to #27.
@copse/streaming-markdownis now deliberately published to public npm via trusted publishing, so the"private": trueguard is obsolete friction:npm pkg delete private), andThis removes the field from
package.jsonand the corresponding strip step fromrelease.yml. Publishing stays controlled by who can authenticate — OIDC-in-CI (the configured trusted publisher) or an authenticated login + 2FA locally — andpublishConfig.access: publickeeps the scoped package public.No effect on the already-published
0.2.0(that tarball was published with the field already stripped).🤖 Generated with Claude Code
Generated by Claude Code