tools/package-release/README.md
When a package contains sufficient changes to justify a release to NPM, follow these instructions to create a new release from the monorepo.
Below are instructions for releasing using Github Workflows (recommended) and the command line. When releasing packages for the first time, release from the command line.
In order to prepare a package for release, a changelog will need to be compiled along with an appropriate version bump.
trunk. You can also choose which packages to prepare for release by supplying them as comma separated values in the input box. To loop through all packages, simply leave the -a flag. Packages that don't have any changes will be skipped and left as is.-a flag, you can pass in a list of packages separated by commas../tools/package-release/bin/dev prepare -a
When making an initial release for a new package, pass the --initial-release flag to signify a new release for a new package.
See more about the prepare script using ./tools/package-release/bin/dev publish --help.
Pull down the latest commits from Github.
Run the release script from monorepo root, first as a dry run.
When making an initial release for a new package, pass the --initial-release flag to signify a new release for a new package.
./tools/package-release/bin/dev publish -a --dry-run
./tools/package-release/bin/dev publish -a
See more about the publish script using ./tools/package-release/bin/dev publish --help.