Skip to content

RELEASE.md

Latest commit

 

History

History
72 lines (53 loc) · 2.63 KB

RELEASE.md

File metadata and controls

72 lines (53 loc) · 2.63 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 and the titles have been updated to ensure they 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.

Unlabeled PRs are left out of the changelog.

Release

Once the prep work is completed, the actual release is straight forward:

  • First, check out an up-to-date master and install the project's dependencies:
git checkout master
git pull
pnpm install

  • Second, ensure that you are logged in to npm as a user with publish access to ember-cli-deploy-s3-index. npm whoami should print your username.

  • Third, 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. Both lerna-changelog and release-it's GitHub release step read it from there.

    For instance:

    export GITHUB_AUTH=abc123def456
  • And last (but not least 😁) do your release.
pnpm release

release-it manages the actual release process. It will prompt you to choose the version number (or pass it directly, e.g. pnpm release minor) 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 committing, tagging, pushing the tag and commits, publishing to npm, and creating the GitHub release.

To preview a release without changing anything, run pnpm release --dry-run.