-
-
Notifications
You must be signed in to change notification settings - Fork 730
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
Upgrade to Rails 7.0 #10440
Upgrade to Rails 7.0 #10440
Conversation
I had a look at the failing system spec. It's on the sales tax by producers report:
The filters In master this appears correctly - pic taken from staging: So, this one is not really spec related, perhaps a code change is needed. Any ideas @abdellani ? (pinging you as you were working on this recently) |
ffdc175
to
d2b208c
Compare
This comment was marked as resolved.
This comment was marked as resolved.
It's always good to run |
@mkllnk I fixed the issue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem was on the "lookup_context.exists?".
I just needed to remove the last "/" from the partial path.
Legend, thanks @abdellani! Once the included PRs are merged I'll rebase this one and we can do some testing. |
be1876a
to
50068fb
Compare
Result of: bundle update --conservative rails railties\ actioncable actionmailbox actionmailer actionpack actiontext\ actionview activejob activemodel activerecord activestorage activesupport
So Rails knows which defaults to apply. https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#rails-version-is-now-included-in-the-active-record-schema-dump
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yay, that seemed pretty painless!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost there!
Hey @mkllnk and everyone chipping in on this ❤️ Performed the suggested tests:
This feels almost too simple compared to other Rails upgrades. I'll do just that, but feel free to merge if others feel otherwise. Ready to go 🚀 |
Actually, this was tested and will be re-tested on release testing - so I see no reason to hold this back. Merging. |
🎉 I wonder if this should bump us to an OFN v4.3 for next release? |
Wow, Rails has become a lot more mature. But I still have that "too easy" feeling as well. We'll see... |
What? Why?
Using the latest version of Rails gives us the latest tools and best compatibility. It speeds up development and unblocks our transition of the asset pipeline.
What should we test?
Release notes
Changelog Category: Technical changes
The title of the pull request will be included in the release notes.
Dependencies
Documentation updates
Follow-up issues to create:
./bin/rails app:update
)