Skip to content

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Feb 1, 2026

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?

✳️ puppeteer-ruby (0.45.6 → 0.50.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ mime-types (indirect, 3.5.2 → 3.7.0) · Repo · Changelog

Release Notes

3.7.0 (from changelog)

  • Deprecated MIME::Type#priority_compare. In a future release, this will be will be renamed to MIME::Type#<=>. This method is used in tight loops, so there is no warning message for either MIME::Type#priority_compare or MIME::Type#<=>.

  • Improved the performance of sorting by eliminating the complex comparison flow from MIME::Type#priority_compare. The old version shows under 600 i/s, and the new version shows over 900 i/s. In sorting the full set of MIME data, there are three differences between the old and new versions; after comparison, these differences are considered acceptable.

  • Simplified the default compare implementation (MIME::Type#<=>) to use the new MIME::Type#priority_compare operation and simplify the fallback to String comparison. This may result in exceptions where there had been none, as explicit support for several special values (which should have caused errors in any case) have been removed.

  • When sorting the result of MIME::Types#type_for, provided a priority boost if one of the target extensions is the type's preferred extension. This means that for the case in #148, when getting the type for foo.webm, the type video/webm will be returned before the type audio/webm, because .webm is the preferred extension for video/webm but not audio/webm (which has a preferred extension of .weba). Added tests to ensure MIME types are retrieved in a stable order (which is alphabetical).

3.6.0 (from changelog)

  • 2 deprecations:

    • Array-based MIME::Type initialization
    • String-based MIME::Type initialization

    Use of these these will result in deprecation warnings.

  • Added logger to the gemspec to suppress a bundled gem warning with Ruby 3.3.5. This warning should not be showing up until Ruby 3.4.0 is released and will be suppressed in Ruby 3.3.6.

  • Reworked the deprecation message code to be somewhat more flexible and allow for outputting certain warnings once. Because there will be at least one other release after 3.6, we do not need to make the type initialization deprecations frequent with this release.

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

Commits

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

↗️ mime-types-data (indirect, 3.2024.0903 → 3.2026.0127) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 async (added, 2.36.0)

🆕 async-http (added, 0.94.2)

🆕 async-pool (added, 0.11.1)

🆕 async-websocket (added, 0.30.0)

🆕 console (added, 1.34.2)

🆕 fiber-annotation (added, 0.2.0)

🆕 fiber-local (added, 1.1.0)

🆕 fiber-storage (added, 1.0.1)

🆕 io-endpoint (added, 0.17.2)

🆕 io-event (added, 1.14.2)

🆕 io-stream (added, 0.11.1)

🆕 metrics (added, 0.15.0)

🆕 protocol-hpack (added, 1.5.1)

🆕 protocol-http (added, 0.58.1)

🆕 protocol-http1 (added, 0.37.0)

🆕 protocol-http2 (added, 0.24.0)

🆕 protocol-rack (added, 0.21.0)

🆕 protocol-url (added, 0.4.0)

🆕 protocol-websocket (added, 0.20.2)

🆕 traces (added, 0.18.2)


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 1, 2026
@coveralls
Copy link

Pull Request Test Coverage Report for Build 21561495409

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 99.361%

Totals Coverage Status
Change from base Build 21551880257: 0.0%
Covered Lines: 778
Relevant Lines: 783

💛 - Coveralls

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