Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Releases should happen only on changed packages, and not for all #52

Open
bertearazvan opened this issue Jul 7, 2021 · 1 comment
Open

Comments

@bertearazvan
Copy link

Hi,

We currently have a monorepo with 2 packages and the way we would like to publish them is by running the semantic-release-multi in the root of our lerna repo and based on the changes in each of the package(together with the angular commit messages), the semantic release should publish only the changed package.

The way we are spotting changes on the packages when we push to git is by having pipelines that get triggered on folder path changes - so for instance if there is a change on packages/icons it will trigger the pipeline devoted to this package.

When running the semantic-release-multi, it publishes both packages under the same version, and a work around for now is to use the --ignore-packages=packages/a/**,packages/b/** flag.

It would be nice if we can specify the list of packages that we want published too, and not only the ones that should be ignored... such that in the pipeline we specify only the given package that should be published instead of ignoring all the other ones.

Or maybe I missed out on something, is the multi-semantic-release supposed to spot the changes per package by itself?

@antongolub
Copy link
Member

Hey, @bertearazvan,

Thanks for your feedback. We're also thinking about smth similar: we're planning to add a special layer/plugin for advanced control of bumping mechanics.
Here's the draft: https://github.com/qiwi/semantic-release-toolkit/blob/add-bumper/packages/bumper/src/main/ts/config.ts
Stay tuned)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants