-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
Feature: Support for independent releases in monorepo #195
Comments
daljitsharma
changed the title
Feature
Feature: Only use latest, single commit to figure out version bump
Nov 26, 2023
Coincidentally, I see someone made a pull request for this issue with a different (better) solution: #193 |
This also looks like another approach: #196 though I think I prefer path filtering as the onus isn't on the engineer to add the correct scope. |
This would be really useful. I agree with @mbarnett-jones, I also would prefer path filtering. |
daljitsharma
changed the title
Feature: Only use latest, single commit to figure out version bump
Feature: Support for independent releases in monorepo
Dec 7, 2023
@mathieudutour would love your input on this. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem:
We have a monorepo with multiple projects inside of it. These projects are completely unrelated with each other. We have workflows to tag and release these projects but these workflows only run when there is push to certain folder in the monorepo. For example say we have
project1/
andproject2/
folders in the monorepo, we can have this workflow to tag and release project1:And a similar workflow for project2 just replacing anywhere it says
project1
withproject2
. This works great, especially since the tag_prefix can figure out the correct release and bump based on that. The problem is all commits in the repo are used to make the release even if they are unrelated. So if we:project1
folder with "feat:" flag -> only project1 workflow runs -> new release for project1 will have minor version upgradeproject2
folder with "fix:" flag -> only project2 workflow runs -> new release for project2 will have minor version upgrade since it is reading all the commits since the last release. The commit that was used to trigger the project1 workflow / release is also used here to determine version.One possible solution (view comments for better possible solution with paths):
We have a strict github merge structure on the monorepos where all PRs are squashed and merged into main as 1 commit. Ideally, if there could be a flag to not view all commits since the last release, but only view the current commit to figure out the proper bump, it would solve our problem. We could have different releases in our monorepo that are not affected by each other
The text was updated successfully, but these errors were encountered: