Skip to content
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

[ruby - main] Update dotenv → 3.0.0 (unknown) #2726

Merged
merged 1 commit into from
Feb 13, 2024

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Feb 13, 2024

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ dotenv (~> 2.2 → ~> 3.0) · Repo · Changelog

Release Notes

3.0.0

See #476 for more details and to discuss this release.

Breaking Changes

  • Ruby >= 3.0 and Rails >= 6.1 are now required. Lock dotenv to ~> 2.0 if you are using an outdated Ruby or Rails version. #466, #471
  • \n is no longer expanded into a newline in quoted strings. Use multi-line strings with real line breaks, or set DOTENV_LINEBREAK_MODE=legacy to preserve the old behavior. @nitsujri #423
  • ENV will be automatically restored between tests (ActiveSupport::TestCase and Rspec). #472, #475
  • Fixed precedence when using Dotenv::Rails.overload. So now .env.development.local will overwrite .env.local, which will overwrite .env.development, which will overwrite .env. @eriklovmo - #460
  • The instrumentation event dotenv.load has been renamed to load.dotenv to properly make use of namespaces in ActiveSupport::Notifications #472

Other improvements

  • All changes to ENV will be logged in Rails apps. #473
  • Fixed an issue where rake loaded development files (.env*development) for test-related tasks. #470
  • Add -i/--ignore option to dotenv CLI to optionally ignore missing files. @stevenharman #463
  • You can customize which files get loaded by setting Dotenv::Rails.files. #468

Deprecations

  • The dotenv-rails gem is now superfluous. It's not technically deprecated yet and will continue to work, but the dotenv gem does the same thing. #468
  • Dotenv::Railtie has been deprecated. Use Dotenv::Rails. #468
  • Dotenv.overload has been replaced with overwrite. overload will still work and is not technically deprecated, but documentation refers to Dotenv.overwrite now. #469

New Contributors

Full Changelog: v2.8.1...v3.0.0.beta

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 70 commits:


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Feb 13, 2024
@tvdeyen tvdeyen merged commit 71cb36d into main Feb 13, 2024
60 checks passed
@tvdeyen tvdeyen deleted the depfu/update/main/dotenv-3.0.0 branch February 13, 2024 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant