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

Commits to one dir generate release of another. #1096

Closed
programad opened this issue Apr 13, 2024 · 2 comments
Closed

Commits to one dir generate release of another. #1096

programad opened this issue Apr 13, 2024 · 2 comments

Comments

@programad
Copy link

programad commented Apr 13, 2024

I am trying to achieve the following:

  • Monorepo
    • packages/gen
    • packages/icons
    • packages/web

The icon package, only has an empty package.json file.
When the package/gen runs, it generates all the contents of the packages/icons folder.
I want to publish ONLY the packages/icons release and npm package.

It works, but only if I commit something to the packages/icons folder.

I want to detect commits on package/gen in order to decide to generate a new release for packages/icons

Is that possible or I must commit something to packages/icons in order for this to work?

Thank you!

@webpro
Copy link
Collaborator

webpro commented Apr 16, 2024

First of all, release-it doesn't have built-in support for monorepos. If you want to publish with separate versioning I'd suggest to run release-it from each package directly and start out from there.

There's quite a few things you could do using hooks, scripts and a fairly large set of built-in options.

If you have a configuration or setup you can share maybe I or others can look at it.

@webpro
Copy link
Collaborator

webpro commented May 8, 2024

👍

@webpro webpro closed this as completed May 8, 2024
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