Skip to content

chore: publish @chatcops/react from the release workflow - #629

Draft
anurag629 wants to merge 1 commit into
devfrom
chore/publish-react
Draft

anurag629 wants to merge 1 commit into
devfrom
chore/publish-react

Conversation

@anurag629

Copy link
Copy Markdown
Member

@chatcops/react (#583) still has "private": true, so changeset publish skips it and the release (#627) wouldn't publish it, while the docs page it adds tells people to install it. This takes the flag off, as #558 did for cli, ingest and the stores, and adds the publishConfig every other package has. It also adds a README, since it's the only package without one and npm shows the README as the package page.

The version PR will publish it as 0.2.0 (0.1.0 plus the minor changeset from #583).

This stays a draft until trusted publishing is set up for @chatcops/react on npm. The package doesn't exist there yet, and the release workflow publishes through OIDC, which can't create a new package.

How I tested this

  • pnpm pack: the tarball has README.md, dist/ and package.json, with no private flag and the widget peer as ^1.1.1 (workspace:^ rewritten).
  • pnpm --filter @chatcops/react test: 22 passed. typecheck passes.

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