Updates on repo release workflow #5568
Replies: 1 comment 4 replies
-
Alrighty -- we've got the first automated release coming out of the monorepo in the editor package (see e758298). What will the bot do? Whenever a PR is merged, it will audit the commits pushed to a particular package area between the commit associated with the last released tag and the current commit. Based on the commit conventions, it'll determine what package version to release and release it. It'll also submit a PR back to update the package.json for the file. 💡 Note: unlike the lerna release process, it will not update the package.json for dependents of the package. This is mostly fine though since we pin to minor versions on all monorepo references (e.g. "@nteract/commutable": "^1.2.3") so patch and minor releases will be handled correctly. For major releases, we probably want to go through and push it out in a separate commit so the right things happen. With this in place, here are some next steps:
|
Beta Was this translation helpful? Give feedback.
-
Hello folks,
After successfully getting semantic-release working on the Lerna mono repo we use for outputs (https://github.com/nteract/outputs), I've been able to configure the same for this monorepo.
From now on, packages will be automatically released if changes have been made to a particular area.
Coupled with this, I've also added back a precommit linter to validate that commits on the repo follow the conventional-commit style so that releases will be versioned appropriately.
There's still some work that needs to be done to support writing back updated version numbers to the repo that I'll do.
One step closer to more automation!
Beta Was this translation helpful? Give feedback.
All reactions