You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Congrats on the new release! I think I found a problem with Rails 6.0. Though I'm a little confused because I'm using dotenv and not dotenv-rails which does seem to have the correct required version number:
...so feel free to close this out if it turns out the problem is that I should be using dotenv-rails instead of dotenv.
Steps to reproduce
Rails 6.0's tagged logging method requires that a block is used. This was introduced in Rails 6.1: rails/rails#38850
When using the new 3.0 release with Rails 6.0, it produces a LocalJumpError because dotenv uses the non-block version which doesn't exist on that older version of Rails:
👋 hey @bensheldon, thanks for reporting the issue.
dotenv 3.0 dropped support for Rails 6.0, but I also updated it to automatically load Rails integration without requiring the dotenv-rails gem. I should probably update the Railtie to not try to load if the Rails version < 6.1.
Congrats on the new release! I think I found a problem with Rails 6.0. Though I'm a little confused because I'm using
dotenv
and notdotenv-rails
which does seem to have the correct required version number:dotenv/dotenv-rails.gemspec
Line 13 in dd40e1c
...so feel free to close this out if it turns out the problem is that I should be using
dotenv-rails
instead ofdotenv
.Steps to reproduce
Rails 6.0's
tagged
logging method requires that a block is used. This was introduced in Rails 6.1: rails/rails#38850When using the new 3.0 release with Rails 6.0, it produces a LocalJumpError because dotenv uses the non-block version which doesn't exist on that older version of Rails:
dotenv/lib/dotenv/rails.rb
Line 87 in dd40e1c
System configuration
dotenv version: 3.0.0
Rails version: 6.0.6.1
Ruby version: 3.3.0
The text was updated successfully, but these errors were encountered: