feat: npm publishing with Changesets#37
Conversation
|
Important Review skippedToo many files! This PR contains 209 files, which is 59 over the limit of 150. ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (209)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Storybook Preview Updated: b8093a4 |
Merging this PR will improve performance by 11.32%
Performance Changes
Comparing Footnotes
|
Summary
@omniview/to@omniviewdev/across the entire monorepo (~200 files)"private": truefrombase-ui,ai-ui, andeditorspackages; add"publishConfig": { "access": "public" }@changesets/cliwith independent versioning, GitHub changelog integration, andbenchmarks/showcaseignoredrelease.ymlGitHub Actions workflow usingchangesets/action— creates Version Packages PRs on merge, publishes to npm when that PR mergesPost-merge setup
NPM_TOKENsecret is already configured. After merge:pnpm changesetto create the first changesetTest plan
pnpm buildpasses for all packagespnpm testpasses (886 tests)npm pack --dry-runshows@omniviewdev/names with correctdist/contents@omniview/references in source/config files