-
Upgrades ruby to 2.7.8
-
I tried upgrading one of my Rails apps to the new version 8.0.0.beta1 yesterday and encountered some failing tests, which appear to relate to breaking changes in the devise-two-factor gem.
I suspe…
-
### Steps to reproduce
after upgrating from rails 5.2 to rails 6.1 and ruby 2.7.2 to 3.3.5 I'm facing some weird errors syntax errors when running the initial migration. The application runs fine and…
xSlok updated
3 weeks ago
-
Looks like the problem in these chunk of code:
```ruby
old = $VERBOSE.dup
$VERBOSE = nil
Object.methods.each do |e|
delegate e, to: :@__object__
end
$VERBOSE = old
```
The error looks like:…
-
After our project was upgraded to Rails 7.1 I've noticed deprecation warnings when using the rails console.
```
[1] pry(main)> test = 'foo'
DEPRECATION WARNING: ActiveRecord::LogSubscriber.reset_…
-
We should upgrade both Ruby and Rails to current versions. This may also help with #3623
-
-
Should we upgrade rails for the next release? The current version is getting pretty old.
Perhaps upgrade for CHORDS v1.2?
-
Can this be updated to support Rails 6.0?
-
We are currently running on version 4.2.10, which is no longer maintained by the core team.
We should gradually upgrade from 4.2 to 5.0 to finally 6.0