-
Notifications
You must be signed in to change notification settings - Fork 81
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
Question/issue how to manage updating local dependencies after versioning? #92
Comments
It has to be handled manually. Unfortunately, automatic upgrading of depending packages arguably falls out of scope of what See this thread for more context: semantic-release/semantic-release#193 |
@CHaNGeTe try multi-semantic-release |
Hi, Do we have any way to solve this now ? |
semantic-release-monorepo doesn't do this either and without this you get duplicate versions when running `npm i` in this repo. See: pmowrer/semantic-release-monorepo#92
First, thanks for this extension.
I wanted to ask how to handle the updating of version numbers on local dependencies.
For example:
semantic-release detects a change on module-A(1.0.0) and releases module-A(1.0.1)
module-B has a dependency on module-A, but package.json still references module-a(1.0.0)
How to include that version bump on the module-B release?
The text was updated successfully, but these errors were encountered: