Skip to content

Latest commit

 

History

History
48 lines (30 loc) · 2.16 KB

RELEASE.md

File metadata and controls

48 lines (30 loc) · 2.16 KB
Raw

Release Process

Releases are mostly automated using release-it and lerna-changelog.

Preparation

Since the majority of the actual release process is automated, the primary remaining task prior to releasing is confirming that all pull requests that have been merged since the last release:

  • have been labeled with the appropriate lerna-changelog labels (see below) and
  • have titles that represent something that would make sense to our users.

Some great information on why this is important can be found at keepachangelog.com, but the overall guiding principle here is that changelogs are for humans, not machines.

When reviewing merged PR's the labels to be used are:

  • breaking - Used when the PR is considered a breaking change.
  • enhancement - Used when the PR adds a new feature or enhancement.
  • bug - Used when the PR fixes a bug included in a previous release.
  • documentation - Used when the PR adds or updates documentation.
  • internal - Used for internal changes that still require a mention in the changelog/release notes.

Release

CI

Click "Run workflow" here.

Manual

  • First, ensure that you have obtained a GitHub personal access token with the repo scope (no other permissions are needed). Make sure the token is available as the GITHUB_AUTH environment variable.

    For instance:

    export GITHUB_AUTH=abc123def456

  • Then do your release. If you're nervous, try pnpm release:debug first.

    pnpm release

release-it manages the actual release process. It will prompt you to to choose the version number after which you will have the chance to hand tweak the changelog to be used (for the CHANGELOG.md and GitHub release), then release-it continues on to tagging, pushing the tag and commits, deploying the docs, etc.