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
Great work guys, with this issue (actually discussion) I hope I can contribute to the library and its support of it as I am big fan of semantic release :)
Discussion
I have projects that have a global configuration, or shared local packages and we have a monorepo structure. Now, the monorepo release works as expected, with no issues, but the top level as a whole does not run.
Based on what I could find, this is intended, as this runs as part of a semantic release. However, I thought of a workaround which was to trigger semantic release for monorepo and traditional repository, which is the issue. When semantic release runs for the top level project, if it is before, semantic release monorepo will see the branch as behind and it if is after the traditional monorepo will see it as behind so, so unless they run in parallel and pull the repository before any of them run the semantic release git change, then it does not work.
Actual behavior
I would love to run semantic release monorepo and if I have 5 workspaces, it will identify 6 releases, including the top level project as a whole and that could be optional.
Issue type
Acknowledgement
Great work guys, with this issue (actually discussion) I hope I can contribute to the library and its support of it as I am big fan of semantic release :)
Discussion
I have projects that have a global configuration, or shared local packages and we have a monorepo structure. Now, the monorepo release works as expected, with no issues, but the top level as a whole does not run.
Based on what I could find, this is intended, as this runs as part of a semantic release. However, I thought of a workaround which was to trigger semantic release for monorepo and traditional repository, which is the issue. When semantic release runs for the top level project, if it is before, semantic release monorepo will see the branch as behind and it if is after the traditional monorepo will see it as behind so, so unless they run in parallel and pull the repository before any of them run the semantic release git change, then it does not work.
Actual behavior
I would love to run semantic release monorepo and if I have 5 workspaces, it will identify 6 releases, including the top level project as a whole and that could be optional.
Steps to reproduce
Specifications
@qiwi/[email protected]
The text was updated successfully, but these errors were encountered: