Skip to content

Prepare the packages for their first npm release as 0.2.0 - #15

Open
nedtwigg wants to merge 1 commit into
mainfrom
npm-publish-prep
Open

nedtwigg wants to merge 1 commit into
mainfrom
npm-publish-prep

Conversation

@nedtwigg

Copy link
Copy Markdown
Member

Makes pgstencil, @pgstencil/auth and @pgstencil/stripe publishable. Nothing publishes on merge: the first release is a manual npm publish of the audited archives, and a follow-up PR adds the trusted-publishing release workflow.

  • Drops "private": true, sets version to 0.2.0 (0.1.0 archives predate the peer-dependency change), and adds publishConfig.access: public so the scoped packages publish publicly.
  • Adds an npm README to each package with its install command and peers, and a disclaimer that it is built for our own applications, 0.x, with no support promise.
  • The auth package's description now lists Microsoft, which it already supports.
  • PACKAGES.md and README.md no longer say the packages are unpublished.

Checked locally:

  • pnpm check (175 tests) and pnpm packages:verify
  • the archives include their READMEs and dist/provenance.json
  • npm publish --dry-run of @pgstencil/auth reports 54 files, public access, and no warnings

🤖 Generated with Claude Code

Drop private, publish the scoped packages publicly, and give each an npm
README with its peers and a no-stability-promise disclaimer. 0.2.0
because 0.1.0 archives predate the peer-dependency change. The auth
description now lists Microsoft, which it supports.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant