- Fork and clone the repository
- Install dependencies with
pnpm install - Make changes
- Run tests with
pnpm test - Create a changeset (see below)
- Submit a pull request
We use changesets to manage our versioning and release process.
Note: Only the
plugin-react-routerpackage is configured for release. Other packages in the monorepo are ignored by the changesets process.
After making your changes, create a changeset to document what you've changed:
pnpm changesetThis will:
- Ask you what kind of change you've made (patch, minor, or major)
- Ask for a summary of your changes
- Create a new file in the
.changesetdirectory
The changeset file should be committed to the repository along with your changes.
- Patch: Bug fixes and small changes that don't affect the public API
- Minor: New features that don't break backward compatibility
- Major: Changes that break backward compatibility
The release process is handled automatically by GitHub Actions when changes are merged to the main branch. The workflow will:
- Create a pull request with all pending changes
- When the PR is merged, publish the new version to npm
If you need to trigger a release manually, run:
pnpm version
pnpm release