You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use changeset in a monorepo where we have multiple apps that use shared local packages.
I don't version those local packages and only version the apps.
When I merge changes to the main branch, one release PR is created for all apps.
That means when I merge the release PR, it's implying I'm releasing all apps at once.
I would like an ability to release each app separately because each app is worked on by a different squad and has different release cycle.
For example, Tuesday app "Foo" would be released, Thursday app "Bar" would be release.
I'm also utilizing publish command for automatic tagging and use the output for automatic deployment.
I would need a different config/command for deploying different app as well.
Let me know if you have further questions.
The text was updated successfully, but these errors were encountered:
mek-earnin
changed the title
[Feature] Ability to create release PR separately for each package
[Feature Request] Ability to create release PR separately for each package
Mar 7, 2025
I use changeset in a monorepo where we have multiple apps that use shared local packages.
I don't version those local packages and only version the apps.
When I merge changes to the main branch, one release PR is created for all apps.
That means when I merge the release PR, it's implying I'm releasing all apps at once.
I would like an ability to release each app separately because each app is worked on by a different squad and has different release cycle.
For example, Tuesday app "Foo" would be released, Thursday app "Bar" would be release.
I'm also utilizing
publish
command for automatic tagging and use the output for automatic deployment.I would need a different config/command for deploying different app as well.
Let me know if you have further questions.
The text was updated successfully, but these errors were encountered: