-
Notifications
You must be signed in to change notification settings - Fork 237
NPM Package Release Process
Didi edited this page Jul 18, 2023
·
3 revisions
This page goes over how to carry out a package release for an existing npm package. The process of releasing an already-bootstrapped package to npm is fairly straightforward and similar for all the published packages in the monorepo.
- Make some meaningful changes to a package in the monorepo.
- Bump the version of the package within the monorepo, this is done with the command
yarn manage-versions
in the root of the monorepo and useslerna
to bump the version of the desired package as well as its version in otherpackage.json
files if it is a dependency in another package in the monorepo. - Submit a pull request.
- Once the PR is merged, the
cd.packages-stable.create-release-drafts.yml
workflow will run. This file creates a release draft for any packages which have a bumped version compared to the latest published version.
Note that the metadata package will automatically be published to npm at this stage.
- Once the release draft is created, it will appear here and you will have to go to the draft, modify the release notes (we usually just copy the text from the CHANGELOG for the package over) and then click publish.
- Lastly, the
handler.publish-release-packages.yml
workflow will run. This file handles the actual publishing of the package to npm.
- Governance Overview
- For Contributors
- Development Process
- Protocol EVMv1 Operations
- Protocol EVMv1 Technical Notes
- Protocol EVMv1 Core Subgraph