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

Question/issue how to manage updating local dependencies after versioning? #92

Closed
CHaNGeTe opened this issue Jun 17, 2020 · 3 comments
Closed

Comments

@CHaNGeTe
Copy link

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?

@pmowrer
Copy link
Owner

pmowrer commented Jun 19, 2020

It has to be handled manually.

Unfortunately, automatic upgrading of depending packages arguably falls out of scope of what semantic-release has been intended to do. It's more likely in the domain of something like lerna or greenkeeper, but I'm not presently aware of any such fully baked solution. In fact, the maintainer of semantic-release has been staunchly opposed to supporting monorepos at all until a solution to this workflow has been proposed (prompting the creation of this workaround-plugin).

See this thread for more context: semantic-release/semantic-release#193

@pmowrer pmowrer closed this as completed Jun 19, 2020
@yyynnn
Copy link

yyynnn commented Oct 12, 2020

@CHaNGeTe try multi-semantic-release

@arvindanta
Copy link

Hi, Do we have any way to solve this now ?

achingbrain added a commit to libp2p/js-libp2p-interfaces that referenced this issue Jan 6, 2022
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
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

4 participants