Fix bug where rails new
used 8.0.0.rc1 instead of the intended 7.2.1
#134
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.
Nextgen currently targets Rails 7.2. However, if someone has a prerelease version of the Rails gems installed, e.g. 8.0.0.rc1, then the
rails new
command issued by Nextgen will use the 8.0.0.rc1 version. This is confusing, because picking "7.2.1" from the interactive menu in Nextgen will end up creating an 8.0 app.Fix by using the RubyGems underscored version argument when calling the
rails new
command:This tells RubyGems the explicit version of the
rails
binary that we want to use.