Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

create-yapp-release-it-setup

yappbox21MIT2.8.1

Simple npm init / yarn create bin package to add release-it setup used by yapp

readme

create-yapp-release-it-setup

Simple npm init / yarn create bin package to add release-it setup used by yapp (inspired by @rwjblue).

This will do the following:

  • add release-it config to the package.json
  • install required dependencies,
  • add a CHANGELOG.md
  • add a RELEASE.md
  • update your repository's labels with our "go to" defaults

Usage

When you want to set up a repo with release-it, you can run:

yarn create yapp-release-it-setup

If you'd like to update an existing repo to use the latest and greatest setup, you can run:

yarn create yapp-release-it-setup --update

If you'd like to run only the label sync, you can do that with:

yarn create yapp-release-it-setup --labels-only

License

This project is licensed under the MIT License.

changelog

v2.8.0 (2020-05-15)

:rocket: Enhancement

:house: Internal

Committers: 2

v2.7.0 (2020-04-28)

:rocket: Enhancement

Committers: 2

v2.6.0 (2020-04-03)

:rocket: Enhancement

  • Upgrade release-it-yarn-workspaces to 1.3.0
  • Update release-it to 13.5.1

v2.5.0 (2020-03-30)

:rocket: Enhancement

  • #52 Add release-it config to disable npm for private packages. (@rwjblue)

Committers: 1

v2.4.0 (2020-03-30)

:rocket: Enhancement

  • #51 Update release-it-yarn-workspaces to prompt for access control with scoped packages (if needed). (@rwjblue)

Committers: 1

v2.3.0 (2020-03-30)

:rocket: Enhancement

:house: Internal

Committers: 2

v2.2.1 (2020-03-23)

:bug: Bug Fix

Committers: 2

v2.2.0 (2020-03-19)

:rocket: Enhancement

  • #38 Update release-it-lerna-changelog minimum version. Ensures changelog presented before version selection is from lerna-changelog. (@rwjblue)

:bug: Bug Fix

  • #37 Ensure existing release-it config is preserved. (@rwjblue)
  • #36 Avoid downgrading release-it / release-it-lerna-changelog. (@rwjblue)
  • #35 Avoid deleting existing GitHub labels when adding new ones. (@rwjblue)
  • #32 Correctly parse repo information. (@rwjblue)

Committers: 2

v2.1.1 (2020-03-12)

:bug: Bug Fix

  • #30 Ensure release-template.md is published with the project. (@rwjblue)

Committers: 1

v2.1.0 (2020-03-10)

:rocket: Enhancement

  • #29 Ensure RELEASE.md mentions yarn install or npm install appropriately. (@rwjblue)

Committers: 1

v2.0.0 (2020-03-10)

:boom: Breaking Change

:rocket: Enhancement

  • #28 Enable release-it-lerna-changelogs launchEditor feature. (@rwjblue)
  • #27 Ensure generated devDependencies match those used for testing. (@rwjblue)
  • #18 Update dependencies / devDependencies to latest. (@rwjblue)
  • #17 Ensure label sync uses same token as release-it and lerna-changelog. (@rwjblue)
  • #15 Use the same GitHub access token for both release-it and lerna-changelog (@jelhan)

Committers: 3

v1.3.0 (2019-08-12)

:rocket: Enhancement

Committers: 1

v1.2.0 (2019-08-12)

:rocket: Enhancement

:bug: Bug Fix

  • #9 Remove release script from package.json. (@rwjblue)

:memo: Documentation

  • #8 Refactor RELEASE.md to mention global install of release-it. (@rwjblue)

Committers: 1

v1.1.1 (2019-06-04)

:bug: Bug Fix

Committers: 1

v1.1.0 (2019-06-04)

:rocket: Enhancement

  • #2 Add GitHub Label Sync setup. (@rwjblue)
  • #1 Automatically add a RELEASE.md file to the repo. (@rwjblue)

Committers: 1