Skip to content

Conversation

@wincent
Copy link
Contributor

@wincent wincent commented Oct 8, 2020

  • Adjust existing .yarnrc files so that the release commit message matches the format used by other packages in this monorepo.
  • Add .yarnrc files for packages that don't have them yet.
  • Configure Lerna (still used in v2 of the js-toolkit) to produce commit messages that match the format produced by yarn; previously they produced commit messages consisting just of the bare version number (eg. see b493e10), which isn't appropriate for a multi-project monorepo.

- Adjust existing .yarnrc files so that the release commit message
  matches the format used by other packages in this monorepo.
- Add .yarnrc files for packages that don't have them yet.
- Configure Lerna (still used in v2 of the js-toolkit) to produce commit
  messages that match the format produced by yarn; previously they
  produced commit messages consisting just of the bare version number
  (eg. see b493e10), which isn't
  appropriate for a multi-project monorepo.
@wincent
Copy link
Contributor Author

wincent commented Oct 8, 2020

I don't think there is any good way to test the Lerna change (I don't think lerna publish has a "dry-run" switch), but I wanted to do a release anyway in order to verify that we actually can do so from the monorepo, so I will try that today.

@wincent
Copy link
Contributor Author

wincent commented Oct 8, 2020

Going to merge this so I can try releasing.

@wincent wincent merged commit 26effa5 into master Oct 8, 2020
@wincent wincent deleted the wincent/yarnrc-consistency branch October 8, 2020 09:56
wincent pushed a commit that referenced this pull request Dec 18, 2020
refactor: improve actions set-up
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants