Skip to content

Latest commit

 

History

History
14 lines (8 loc) · 660 Bytes

release.md

File metadata and controls

14 lines (8 loc) · 660 Bytes

Release

Manually releasing all the packages of a monorepo can be as challenging as inappropriate. For such a reason we rely on changesets, GH actions and as less as possible manual steps.

Requirements

  • Privileges to trigger GH actions.
  • Proper changesets to be deployed.

Steps

Publish npm packages

Run the publish GH action. This should generate a PR with version bumps and changelogs updates. After carefully reviewing the PR, merge it and run the publish action again, passing an NPM_TOKEN with privileges to publish in the @inversifyjs npm org. This should trigger an attempt to publish npm packages and generate github releases