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

Deprecate array and string type initialization #183

Merged
merged 1 commit into from
Oct 2, 2024

Conversation

halostatue
Copy link
Member

  • 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.

@halostatue halostatue force-pushed the mime-types-3.6-deprecations branch 3 times, most recently from 70e85b4 to aa67cb0 Compare September 22, 2024 20:36
@halostatue halostatue force-pushed the mime-types-3.6-deprecations branch 3 times, most recently from 65fa04e to 808a701 Compare October 2, 2024 01:54
- 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.
@halostatue halostatue enabled auto-merge (rebase) October 2, 2024 01:58
@halostatue halostatue merged commit 8512c15 into main Oct 2, 2024
53 of 56 checks passed
@halostatue halostatue deleted the mime-types-3.6-deprecations branch October 2, 2024 02:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant