search

nodunayo / speakerline

Showcasing speakers' proposals and timelines in an effort to demystify the CFP process and help new speakers get started.
http://speakerline.io
MIT License
73 stars 26 forks source link

🚨 [security] Update dotenv-rails 2.8.1 → 3.1.0 (major) #552

Closed depfu[bot] closed 2 months ago

depfu[bot] commented 4 months ago

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

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

What changed?

✳️ dotenv-rails (2.8.1 → 3.1.0) · Repo · Changelog

Release Notes

3.1.0

What's Changed

  • Fix regression with semantic-logger, allow setting custom logger by @bkeepers in #494 
    # config/application.rb

# Set a custom dotenv logger
Dotenv::Rails.logger = MyCustomLogger.new

module YourApp
  class Application < Rails::Application
    # …
  end
end

Full Changelog: v3.0.3...v3.1.0

3.0.3

What's Changed

New Contributors

Full Changelog: v3.0.2...v3.0.3

3.0.2

What's Changed

  • Restore ability to mutate Dotenv::Rails.files by @bkeepers in #486

Full Changelog: v3.0.1...v3.0.2

3.0.1

What's Changed

  • Disable autorestore if using climate_control or ice_age by @bkeepers in #483
  • Join files to Rails.root at load time by @bkeepers in #484
  • Manually check optional Rails dependency version by @bkeepers in #481

Full Changelog: v3.0.0...v3.0.1

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 more commits than we can show here.

↗️ bigdecimal (indirect, 3.1.5 → 3.1.6) · Repo · Changelog

Release Notes

3.1.6

What's Changed

  • Correctly computing loop iterations in BigDecimal#sqrt by @z2-2z in #280
  • Workaround for test-bundled-gems at ruby/ruby repo by @hsbt in #283
  • Add LICENSE file to gem files by @oleksii-leonov in #282
  • Refine test code related unsupported Ruby version by @hsbt in #284

New Contributors

Full Changelog: v3.1.5...v3.1.6

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

Commits

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

↗️ dotenv (indirect, 2.8.1 → 3.1.0) · Repo · Changelog

Release Notes

3.1.0

What's Changed

  • Fix regression with semantic-logger, allow setting custom logger by @bkeepers in #494 
    # config/application.rb

# Set a custom dotenv logger
Dotenv::Rails.logger = MyCustomLogger.new

module YourApp
  class Application < Rails::Application
    # …
  end
end

Full Changelog: v3.0.3...v3.1.0

3.0.3

What's Changed

New Contributors

Full Changelog: v3.0.2...v3.0.3

3.0.2

What's Changed

  • Restore ability to mutate Dotenv::Rails.files by @bkeepers in #486

Full Changelog: v3.0.1...v3.0.2

3.0.1

What's Changed

  • Disable autorestore if using climate_control or ice_age by @bkeepers in #483
  • Join files to Rails.root at load time by @bkeepers in #484
  • Manually check optional Rails dependency version by @bkeepers in #481

Full Changelog: v3.0.0...v3.0.1

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 more commits than we can show here.

↗️ io-console (indirect, 0.7.1 → 0.7.2) · Repo

Release Notes

0.7.2

What's Changed

New Contributors

Full Changelog: v0.7.1...v0.7.2

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

Commits

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

↗️ irb (indirect, 1.11.1 → 1.11.2) · Repo

Release Notes

1.11.2

What's Changed

🐛 Bug Fixes

🛠 Other Changes

New Contributors

Full Changelog: v1.11.1...v1.11.2

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

Commits

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

↗️ minitest (indirect, 5.21.2 → 5.22.2) · Repo · Changelog

Release Notes

5.22.2 (from changelog)

  • 1 bug fix:

    • Third time’s a charm? Remember: ‘ensure’ is almost always the wrong way to go (for results… it’s great for cleaning up).

5.22.1 (from changelog)

  • 1 bug fix:

    • Don’t exit non-zero if no tests ran and no filter (aka, the test file is empty). (I’m starting to think the exit 1 thing for @tenderlove was a mistake…)

5.22.0 (from changelog)

  • 1 minor enhancement:

    • Added “did you mean” output if your –name filter matches nothing. (tenderlove)

  • 2 bug fixes:

    • Big cleanup of test filtering. Much prettier / more functional.

    • Fix situation where Assertion#location can’t find the location. (pftg)

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

Commits

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

↗️ rack (indirect, 2.2.8 → 2.2.8.1) · Repo · Changelog

Security Advisories 🚨

🚨 Possible Denial of Service Vulnerability in Rack Header Parsing

There is a possible denial of service vulnerability in the header parsing
routines in Rack. This vulnerability has been assigned the CVE identifier
CVE-2024-26146.

Versions Affected: All. Not affected: None Fixed Versions: 2.0.9.4, 2.1.4.4, 2.2.8.1, 3.0.9.1

Impact

Carefully crafted headers can cause header parsing in Rack to take longer than
expected resulting in a possible denial of service issue. Accept and
Forwarded headers are impacted.

Ruby 3.2 has mitigations for this problem, so Rack applications using
Ruby 3.2 or newer are unaffected.

Releases

The fixed releases are available at the normal locations.

Workarounds

There are no feasible workarounds for this issue.

🚨 Possible DoS Vulnerability with Range Header in Rack

There is a possible DoS vulnerability relating to the Range request header in
Rack. This vulnerability has been assigned the CVE identifier CVE-2024-26141.

Versions Affected: >= 1.3.0. Not affected: < 1.3.0 Fixed Versions: 3.0.9.1, 2.2.8.1

Impact

Carefully crafted Range headers can cause a server to respond with an
unexpectedly large response. Responding with such large responses could lead
to a denial of service issue.

Vulnerable applications will use the Rack::File middleware or the
Rack::Utils.byte_ranges methods (this includes Rails applications).

Releases

The fixed releases are available at the normal locations.

Workarounds

There are no feasible workarounds for this issue.

🚨 Denial of Service Vulnerability in Rack Content-Type Parsing

There is a possible denial of service vulnerability in the content type
parsing component of Rack. This vulnerability has been assigned the CVE
identifier CVE-2024-25126.

Versions Affected: >= 0.4 Not affected: < 0.4 Fixed Versions: 3.0.9.1, 2.2.8.1

Impact

Carefully crafted content type headers can cause Rack’s media type parser to
take much longer than expected, leading to a possible denial of service
vulnerability.

Impacted code will use Rack’s media type parser to parse content type headers.
This code will look like below:

request.media_type

## OR
request.media_type_params

## OR
Rack::MediaType.type(content_type)

Some frameworks (including Rails) call this code internally, so upgrading is
recommended!

All users running an affected release should either upgrade or use one of the
workarounds immediately.

Releases

The fixed releases are available at the normal locations.

Workarounds

There are no feasible workarounds for this issue.

Release Notes

2.2.8.1

What's Changed

  • Fixed ReDoS in Accept header parsing [CVE-2024-26146]
  • Fixed ReDoS in Content Type header parsing [CVE-2024-25126]
  • Reject Range headers which are too large [CVE-2024-26141]

Full Changelog: v2.2.8...v2.2.8.1

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

Commits

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

↗️ reline (indirect, 0.4.2 → 0.4.3) · Repo

Release Notes

0.4.3

What's Changed

✨ Enhancements

🛠 Other Changes

  • Add metadata for rubygems.org by @m-nakamura145 in #638
  • [Feature #16495] Do not include a backtick in error messages and backtraces by @hsbt in #640
  • Bump version to v0.4.3 by @st0012 in #642

New Contributors

Full Changelog: v0.4.2...v0.4.3

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

Commits

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

↗️ thor (indirect, 1.3.0 → 1.3.1) · Repo · Changelog

Release Notes

1.3.1

What's Changed

New Contributors

Full Changelog: v1.3.0...v1.3.1

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

Commits

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

↗️ zeitwerk (indirect, 2.6.12 → 2.6.13) · Repo · Changelog

Release Notes

2.6.13 (from changelog)

  • There is a new experimental null inflector that simply returns its input unchanged:

    loader.inflector = Zeitwerk::NullInflector.new

    Projects using this inflector are expected to define their constants in files and directories with names exactly matching them:

    User.rb       -> User
HTMLParser.rb -> HTMLParser
Admin/Role.rb -> Admin::Role

    Please see its documentation for further details.

  • Documentation improvements.

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

Commits

See the full diff on Github. The new version differs by 13 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[bot] commented 2 months ago

Closed in favor of #558.