-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Changing gemspec unlocks all dependencies #6746
Comments
Is it possible it’s only transitive dependencies of the gemspec being unlocked? |
Yes, that's very likely, actually, since that gemspec has a bunch of dependencies: https://github.com/decidim/decidim/blob/15a0112c911c00f9215eff947eff6beabbab9ff9/decidim-core/decidim-core.gemspec#L21-L66. |
I ran through @deivid-rodriguez's steps and got the same result. One of the dependencies updated is |
@Ferdy89 Yeah, I think that's what @segiddins meant by "transitive dependencies of the gemspec", and I think it's unexpected (even if the updated dependencies come from the same gemspec). |
I ran into the very similar issue today - only I don't even need to change the .gemspec file. |
Closing in favor of #6967! |
I've seen this issue a lot of times but I was always lazy to report it. The issue is that on the decidim repo, when I change a gemspec requirement and run
bundle install
, every dependency seem to be unlocked and the command effectively works asbundle update
.In order to reproduce:
rectify
requirement here to~> 0.13.0
.bundle install
.Every gem seems to be updated, and not just
rectify
and its dependencies.The text was updated successfully, but these errors were encountered: