pivotal / LicenseFinder

Find licenses for your project's dependencies.
MIT License
1.73k stars 340 forks source link

chore(deps-dev): update mime-types requirement from = 3.4.1 to = 3.5.1 #1002

Closed dependabot[bot] closed 9 months ago

dependabot[bot] commented 1 year ago

Updates the requirements on mime-types to permit the latest version.

Changelog

Sourced from mime-types's changelog.

3.5.1 / 2023-08-21

  • 1 bug fix:

    • Better handle possible line-termination strings (legal in Unix filenames) such as \n in MIME::Types.type_for. Reported by ooooooo-q in #177[], resolved in #178[].

3.5.0 / 2023-08-07

  • 1 minor enhancement:

    • Robb Shecter changed the default log level for duplicate type variant from warn to debug in #170[]. This works because MIME::Types.logger is intended to fit the ::Logger interface, and the default logger (WarnLogger) is a subclass of ::Logger that passes through to Kernel.warn.

      • Further consideration has changed cache load messages from warn to error and deprecation messages from warn to debug.
  • 1 bug fix:

    • Added a definition of MIME::Type#hash. Contributed by Alex Vondrak in #167[], fixing #166[].
  • Dependency and CI updates:

    • Update the .github/workflows/ci.yml workflow to test Ruby 3.2 and more reliably test certain combinations rather than depending on exclusions.

    • Change .standard.yml configuration to format for Ruby 2.3 as certain files are not properly detected with Ruby 2.0.

      • Change from hoe-git to hoe-git2 to support Hoe version 4.

      • Apply standardrb --fix.

      • The above changes have resulted in the Soft deprecation of Ruby versions below 2.6. Any errors reported for Ruby versions 2.0, 2.1, 2.2, 2.3, 2.4, and 2.5 will be resolved, but maintaining CI for these versions is unsustainable.

3.4.1 / 2021-11-16

  • 1 bug fix:

    • Fixed a Ruby < 2.3 incompatibility introduced by the use of standardrb, where <<- heredocs were converted to <<~ heredocs. These have been reverted back to <<- with the indentation kept and a .strip call

... (truncated)

Commits
  • a545cd2 Fix gemspec
  • 9583a38 Move truffleruby{,+graalvm}-head to ubuntu-22.04
  • 27940f2 Handle \n in MIME::Types.type_for
  • 9d58c6e Add dogweather's name to Contributing.md
  • 327016e Update release documentation for logging changes
  • 052c77a Change logging to debug level.
  • 1862bd7 Prepare for 3.5.0
  • b9382fe Various upgrades
  • 0bf7805 Merge pull request #169 from petergoldstein/feature/add_ruby_3_2_to_ci
  • 6910344 Add fail-fast: false
  • Additional commits viewable in compare view


You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

cf-gitbot commented 1 year ago

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.