Repository navigation
Read the Gemfile that BUNDLE_GEMFILE names - #23
Merged
Merged
Conversation
Dual-boot apps keep the next Rails in Gemfile.next and Gemfile.next.lock. The tool always read Gemfile.lock, so it could only audit the boot the app runs today. It now reads the Gemfile and lockfile that BUNDLE_GEMFILE names, as Bundler does, and messages name the lockfile it actually read.
This was referenced Oct 13, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
BUNDLE_GEMFILE=Gemfile.next rails-preflightnow audits the Gemfile and lockfile it names. Dual-boot apps keep the next Rails inGemfile.nextandGemfile.next.lock, and the tool always readGemfile.lock, so it could only audit the boot the app runs today.Gemfile.locknow name the lockfile that was actually read.