-
-
Notifications
You must be signed in to change notification settings - Fork 931
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
Bump rails to 8.0.1 #5279
base: master
Are you sure you want to change the base?
Bump rails to 8.0.1 #5279
Conversation
068de22
to
8b64ba5
Compare
0fb1d12
to
d74cfc1
Compare
I manually spot checked a few pages to make sure dev is still working. The tests are otherwise much better than manual checking, so this is probably safe. |
36c888f
to
9a50924
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5279 +/- ##
=======================================
Coverage 97.13% 97.13%
=======================================
Files 457 457
Lines 9567 9567
=======================================
Hits 9293 9293
Misses 274 274 ☔ View full report in Codecov by Sentry. |
d02eb2c
to
927534e
Compare
I set the framework default to 8.0. None of the changes look like they will affect us. I expect the tests to cover us (and if they don't, then we won't find it by enabling them one at a time). |
c0fa1a8
to
83f1578
Compare
I have reverted |
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.
I feel good about this. I mentioned elsewhere but I'll summarize here:
- Our tests fail on rails 7.2 (master) with "7.2" framework defaults due to a test job order problem. (it impacts 2 tests in admin that rely on a job running in the middle of the test run)
- They pass on rails 7.2 (master) with "7.1" defaults
- They pass on rails 8.0 (this branch) with "7.2" and "8.0" defaults.
This implies to me that there is a bug in the test job runner (or a change in behavior) in rails 7.2 with default settings. It was seemingly fixed, for how we use them, in rails 8.0.
Therefore I don't think it makes sense to step to "7.2" framework defaults before going to rails 8.0 with "7.2" defaults because the work to fix the tests is ultimately unnecessary.
🚀
ff2ffa5
to
86b4889
Compare
Waiting for 8.0.1, but I'll leave this open since the upgrade will be about the same. |
f7ebc74
to
e7a22bc
Compare
Updated to 8.0.1 🎉 |
What about this?
|
@simi that's in the framework defaults. I'm fine with enabling them now but there was hesitation with jumping to them right away. Maybe one deploy with 7.2 and then switch to 8.0? |
I prefer no deprecation warnings. Those are super annoying for developers (and mostly for new contributors). |
b32f76f
to
a840df9
Compare
I managed to find a place to put the line to remove the deprecation warning. Leaving it in the new_framework_defaults file doesn't successfully suppress the warning. |
Run rails app:update, set framework defaults = 7.2 Bumps [rails-i18n](https://github.com/svenfuchs/rails-i18n) and [rails](https://github.com/rails/rails). These dependencies needed to be updated together. Updates `rails-i18n` from 7.0.10 to 8.0.1 - [Changelog](https://github.com/svenfuchs/rails-i18n/blob/master/CHANGELOG.md) - [Commits](https://github.com/svenfuchs/rails-i18n/commits) Updates `rails` from 7.2.1.1 to 8.0.1 - [Release notes](https://github.com/rails/rails/releases) - [Commits](rails/rails@v7.2.1.1...v8.0.1) --- updated-dependencies: - dependency-name: rails-i18n dependency-type: direct:production update-type: version-update:semver-major - dependency-name: rails dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
a840df9
to
c906f18
Compare
Bumps rails-i18n and rails. These dependencies needed to be updated together.
Updates
rails-i18n
from 7.0.10 to 8.0.1Changelog
Sourced from rails-i18n's changelog.
Commits
Updates
rails
from 7.2.1.1 to 8.0.1Release notes
Sourced from rails's releases.
... (truncated)
Commits
dd8f718
Preparing for 8.0.0 releasef88e6ae
Merge pull request #53550 from tysongach/devcontainer-links43425c8
Bump deprecation message to 8.138bf52d
Add yarn.lock to allowed dirty files3de9afc
Merge pull request #53546 from matthewd/dst_deprecation_fixebcb66e
Merge pull request #53542 from Uaitt/remove-redundant-period-in-security-guides4f042a8
Merge pull request #53520 from Earlopain/fix-backtrace-env-gem-paths74608e5
Merge pull request #53533 from Earlopain/no-docs-for-rackup8ee2d3e
Merge pull request #53504 from SleeplessByte/fix/anchor-scroll-mobile473f2b2
Merge pull request #53515 from k-tsuchiya-jp/fix-53467Most Recent Ignore Conditions Applied to This Pull Request
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Note: Dependabot was ignoring updates to this dependency, but since you've updated it yourself we've started tracking it for you again. 🤖
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)