Upgrade to Rails 8.1 beta #140
Merged
Conversation
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
maebeale
reviewed
Sep 13, 2025
|
|
||
| gem 'sprockets-rails', '~> 3.2.2' | ||
| gem "activerecord-trilogy-adapter" # for mysql installation | ||
| gem 'trilogy' |
Collaborator
There was a problem hiding this comment.
wasn't this already in there?
Collaborator
Author
There was a problem hiding this comment.
I think trilogy was indirectly loaded as a dependency for activerecord-trilogy-adapter. That is no longer needed as of rails 7.1+, so I added just the trilogy adapter.
elasticspoon
force-pushed
the
feature/rails81beta
branch
3 times, most recently
from
220133f to
3727b50
Compare
elasticspoon
force-pushed
the
feature/rails81beta
branch
from
3727b50 to
6624e51
Compare
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.
What is the goal of this PR and why is this important?
We are upgrading to rails 8.1.beta1 to bring the framework up to date.
How did you approach the change?
I upgraded to rails 7.0, 7.1, 7.2 and 8.0 and made sure the tests were passing and the app looked good for users and admins.
Running everything in docker containers.
Anything else to add?
We want to try this in staging to make sure it works well outside of the dev containers.
Thanks @johnpaulashenfelter for the commits and helping with the upgrade!