This repository uses Changesets for versioning and GitHub Actions for CI and publishing.
- Run
pnpm changesetin any PR that changes@abstract-foundation/mpp. - Merge changesets into
main. - The
Release PRworkflow opens or updates aVersion Packagespull request. - Merge the
Version Packagespull request. - A push to
maintriggers thePublishworkflow. - The workflow compares
packages/mpp/package.jsonto the version currently on npm and only continues when the local version is unpublished. - For unpublished versions, the workflow verifies the merged commit, waits for
approval on the protected
npmenvironment, and then publishes to npm.
Create a GitHub environment named npm and configure:
- Required reviewers for the publish approval gate
- Optional
prevent self-reviewif you want a second person to approve every release
The publish job references that environment directly in
.github/workflows/publish.yml.
Configure npm trusted publishing for @abstract-foundation/mpp:
- Repository owner:
Abstract-Foundation - Repository:
mpp-abstract - Workflow filename:
publish.yml - Environment name:
npm
This workflow uses npm trusted publishing with GitHub OIDC, so it does not need
an NPM_TOKEN.
The repo-local automation is already configured with changesets/action, which
creates and maintains the Version Packages pull request.
If you also want PR reminder comments from the Changesets GitHub App, install the Changesets bot separately from GitHub Apps. That install cannot be done from the repository files alone.