-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changesets setup + auto-publish to npm #922
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 9 Ignored Deployments
|
574e09c
to
3c600d6
Compare
- link commits, PRs, and users in generated changelogs
- install @changesets/cli and @changesets/changelog-github generator
The workflow creates a PR with version bumps and related changelog files' updates, each time a commit containing a changeset file is added on the main branch.
3c600d6
to
3366016
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@olayway LGTM. I guess we have to merge it in order to be able to test it.
Closes #905
Summary
This PR sets up changesets with the aim to simplify the process of documenting changes committed to the codebase, as well as automating versioning packages and publishing them to npm.
Changes
.github/workflows/release.yml
: The workflow creates a PR with version bumps and related changelogfiles' updates, each time a commit containing changeset
file(s) is added to the main branch. After merging this auto-generated PR, this workflow will also auto-publish the released packages to npm and add git tags.
package.json
:changeset
: should be run to generate changeset files, that describe changes made to the code,prerelease
: runs linting and testing on packages affected by the changes in a PRrelease
: runschangeset publish
and is used by therelease
workflow then the above-mentioned auto-generated PR is merged to the main branchTODOs