Skip to content

Latest commit

 

History

History
52 lines (31 loc) · 1.83 KB

RELEASE.md

File metadata and controls

52 lines (31 loc) · 1.83 KB
Raw

This document outlines the process for creating a new BLT release.

To perform a release:

  1. Check build statuses
  2. Run tests locally.
  3. Generate and commit updated CHANGELOG.md.
  4. Create a release

Check build statuses

Testing

Prerequisites

In order to use these testing instructions:

  • BLT's dependencies must be installed by running composer install in the BLT directory.
  • You must install VirtualBox and Vagrant. See Drupal VM for more information.

Execute tests

./vendor/bin/robo test

Update Canary

Submit a pull request to Canary with BLT updated to HEAD. Ensure tests pass.

Update CHANGELOG.md

Prerequisites

  • BLT's dependencies must be installed by running composer install in the BLT directory.
  • Procure a github api token.
  • Determine the version of your future release.

Execute command

Then, generate your release notes via:

./vendor/bin/robo release-notes [tag] [token]

Create a release

To both generate release notes and also create a new release on GitHub, execute:

./vendor/bin/robo release [tag] [token]