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

Only Gemfile_next.lock Is Getting Updated After Installing BootBoot #63

Open
gregfletch opened this issue May 12, 2023 · 2 comments
Open

Comments

@gregfletch
Copy link

After installing BootBoot, when I run bundle update (regardless of whether or not I have DEPENDENCIES_NEXT environment variable set), only the Gemfile_next.lock is being updated, Gemfile.lock is unchanged. This is causing issues on CI when running the current version as it is pulling the older version(s) of gems from the Gemfile.lock. I've noticed that running Bundler.default_lockfile always returns Gemfile_next.lock regardless of whether the DEPENDENCIES_NEXT environment variable is set.

Just wondering what the expected behaviour is - like from the docs, it sounds like bundle update should be updating both lock files. Is there something I'm missing in order to get BootBoot to update both lock files?

@deivid-rodriguez
Copy link
Contributor

Can you try again using Bundler 2.4.22?

@gregfletch
Copy link
Author

With Bundler 2.4.22, if I update a specific gem (i.e. bundle update rails) that seems to work as expected and updates both lock files. However, if I attempt to update all outdated gems (i.e. bundle update), it seems to still only update the Gemfile_next.lock file.

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

2 participants