mime-types-data 3.2024.1105 → 3.2026.0127

data/lib/mime/types/data.rb

@@ -3,7 +3,7 @@
 module MIME
   class Types
     module Data
-      VERSION = "3.2024.1105"
+      VERSION = "3.2026.0127"
 
       # The path that will be used for loading the MIME::Types data. The
       # default location is __FILE__/../../../../data, which is where the data

data/licences/dco.txt

@@ -0,0 +1,34 @@
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.

metadata

@@ -1,14 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: mime-types-data
 version: !ruby/object:Gem::Version
-  version: 3.2024.1105
+  version: 3.2026.0127
 platform: ruby
 authors:
 - Austin Ziegler
-autorequire:
 bindir: bin
 cert_chain: []
-date: 2024-11-06 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: hoe
@@ -25,81 +24,39 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '4.0'
 - !ruby/object:Gem::Dependency
-  name: hoe-doofus
+  name: hoe-halostatue
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.0'
-- !ruby/object:Gem::Dependency
-  name: hoe-gemspec2
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.1'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.1'
-- !ruby/object:Gem::Dependency
-  name: hoe-git2
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.7'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.7'
-- !ruby/object:Gem::Dependency
-  name: hoe-rubygems
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.0'
+        version: '2.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.0'
+        version: '2.0'
 - !ruby/object:Gem::Dependency
   name: mime-types
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - ">"
       - !ruby/object:Gem::Version
-        version: 3.4.0
+        version: 3.6.2
     - - "<"
       - !ruby/object:Gem::Version
-        version: '4'
+        version: '5'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - ">"
       - !ruby/object:Gem::Version
-        version: 3.4.0
+        version: 3.6.2
     - - "<"
       - !ruby/object:Gem::Version
-        version: '4'
+        version: '5'
 - !ruby/object:Gem::Dependency
   name: nokogiri
   requirement: !ruby/object:Gem::Requirement
@@ -148,48 +105,30 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '1.0'
-- !ruby/object:Gem::Dependency
-  name: rdoc
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '4.0'
-    - - "<"
-      - !ruby/object:Gem::Version
-        version: '7'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '4.0'
-    - - "<"
-      - !ruby/object:Gem::Version
-        version: '7'
-description: |-
-  mime-types-data provides a registry for information about MIME media type
-  definitions. It can be used with the Ruby mime-types library or other software
-  to determine defined filename extensions for MIME types, or to use filename
-  extensions to look up the likely MIME type definitions.
+description: mime-types-data provides a registry for information about MIME media
+  type definitions. It can be used with the Ruby mime-types library or other software
+  to determine defined filename extensions for MIME types, or to use filename extensions
+  to look up the likely MIME type definitions.
 email:
 - halostatue@gmail.com
 executables: []
 extensions: []
 extra_rdoc_files:
-- Code-of-Conduct.md
-- Contributing.md
-- History.md
-- Licence.md
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- CONTRIBUTING.md
+- CONTRIBUTORS.md
+- LICENCE.md
 - Manifest.txt
 - README.md
 - SECURITY.md
+- licences/dco.txt
 files:
-- Code-of-Conduct.md
-- Contributing.md
-- History.md
-- Licence.md
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- CONTRIBUTING.md
+- CONTRIBUTORS.md
+- LICENCE.md
 - Manifest.txt
 - README.md
 - Rakefile
@@ -203,31 +142,21 @@ files:
 - data/mime.flags.column
 - data/mime.friendly.column
 - data/mime.pext.column
+- data/mime.spri.column
 - data/mime.use_instead.column
 - data/mime.xrefs.column
 - lib/mime-types-data.rb
 - lib/mime/types/data.rb
-- types/application.yaml
-- types/audio.yaml
-- types/chemical.yaml
-- types/conference.yaml
-- types/drawing.yaml
-- types/example.yaml
-- types/font.yaml
-- types/haptics.yaml
-- types/image.yaml
-- types/message.yaml
-- types/model.yaml
-- types/multipart.yaml
-- types/text.yaml
-- types/video.yaml
-- types/world.yaml
+- licences/dco.txt
 homepage: https://github.com/mime-types/mime-types-data/
 licenses:
 - MIT
 metadata:
+  homepage_uri: https://github.com/mime-types/mime-types-data/
+  bug_tracker_uri: https://github.com/mime-types/mime-types-data/issues
+  source_code_uri: https://github.com/mime-types/mime-types-data/
+  changelog_uri: https://github.com/mime-types/mime-types-data/blob/main/CHANGELOG.md
   rubygems_mfa_required: 'true'
-post_install_message:
 rdoc_options:
 - "--main"
 - README.md
@@ -244,8 +173,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.23
-signing_key:
+rubygems_version: 4.0.4
 specification_version: 4
 summary: mime-types-data provides a registry for information about MIME media type
   definitions

data/Code-of-Conduct.md

@@ -1,128 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
-identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-- Demonstrating empathy and kindness toward other people
-- Being respectful of differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the overall
-  community
-
-Examples of unacceptable behavior include:
-
-- The use of sexualized language or imagery, and sexual attention or advances of
-  any kind
-- Trolling, insulting or derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or email address,
-  without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official email address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at [INSERT CONTACT
-METHOD]. All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of
-actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or permanent
-ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the
-community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-<https://www.contributor-covenant.org/faq>. Translations are available at
-<https://www.contributor-covenant.org/translations>.
-
-[homepage]: https://www.contributor-covenant.org
-[Mozilla CoC]: https://github.com/mozilla/diversity

data/Contributing.md

@@ -1,203 +0,0 @@
-# Contributing
-
-Contributions to mime-types-data is encouraged in any form: a bug report, new
-MIME type definitions, or additional code to help manage the MIME types. As with
-many of my projects, I have a few suggestions for improving the chance of
-acceptance of your code contributions:
-
-- The support files are written in Ruby and should remain in the coding style
-  that already exists, and I use hoe for releasing the mime-types-data RubyGem.
-- Use a thoughtfully-named topic branch that contains your change. Rebase your
-  commits into logical chunks as necessary.
-- Use [quality commit messages][qcm].
-- Do not change the version number; when your patch is accepted and a release is
-  made, the version will be updated at that point.
-- Submit a GitHub pull request with your changes.
-- New or changed behaviours require new or updated documentation.
-
-Although mime-types-data was extracted from the [Ruby mime-types][rmt] gem and
-the support files are written in Ruby, the _target_ of mime-types-data is any
-implementation that wishes to use the data as a MIME types registry, so I am
-particularly interested in tools that will create a mime-types-data package for
-other languages.
-
-## Adding or Modifying MIME Types
-
-The Ruby mime-types gem loads its data from files encoded in the `data`
-directory in this gem by loading `mime-types-data` and reading
-MIME::Types::Data::PATH. These files are compiled files from the collection of
-data in the `types` directory. Pull requests that include changes to these files
-will require amendment to revert these files.
-
-New or modified MIME types should be edited in the appropriate YAML file under
-`types`. The format is as shown below for the `application/xml` MIME type in
-`types/application.yml`.
-
-```yaml
-- !ruby/object:MIME::Type
-  content-type: application/xml
-  encoding: 8bit
-  extensions:
-    - xml
-    - xsl
-  references:
-    - IANA
-    - RFC3023
-  xrefs:
-    rfc:
-      - rfc3023
-  registered: true
-```
-
-There are other fields that can be added, matching the fields discussed in the
-documentation for MIME::Type. Pull requests for MIME types should just contain
-the changes to the YAML files for the new or modified MIME types; I will convert
-the YAML files to JSON prior to a new release. I would rather not have to verify
-that the JSON matches the YAML changes, which is why it is not necessary to
-convert for the pull request.
-
-If you are making a change for a private fork, use `rake convert:yaml:json` to
-convert the YAML to JSON, or `rake convert:yaml:columnar` to convert it to the
-new columnar format.
-
-### Updating Types from the IANA or Apache Lists
-
-If you are maintaining a private fork and wish to update your copy of the MIME
-types registry used by this gem, you can do this with the rake tasks:
-
-```sh
-$ rake mime:iana
-$ rake mime:apache
-```
-
-#### A Note on Provisional Types
-
-Provisionally registered types from IANA are contained in the `types/*.yaml`
-files. Per IANA,
-
-> This registry, unlike some other provisional IANA registries, is only for
-> temporary use. Entries in this registry are either finalized and moved to the
-> main media types registry or are abandoned and deleted. Entries in this
-> registry are suitable for use for development and test purposes only.
-
-Provisional types are rewritten when updated, so pull requests to manually
-customize provisional types (such as with extensions) are considered lower
-priority. It is recommended that any updates required to the data be performed
-in your application if you require provisional types.
-
-## Development Dependencies
-
-## Test Dependencies
-
-mime-types-data uses Ryan Davis’s [Hoe][hoe] to manage the release process, and
-it adds a number of rake tasks. You will mostly be interested in `rake`, which
-runs tests the same way that `rake test` does.
-
-To assist with the installation of the development dependencies for mime-types,
-I have provided the simplest possible Gemfile pointing to the (generated)
-`mime-types-data.gemspec` file. This permits `bundle install` for dependencies.
-If you already have `hoe` installed, you can accomplish the same thing with
-`rake newb`. This task will install any missing dependencies, run the tests, and
-generate the RDoc.
-
-You can run tests with code coverage analysis by running `rake test:coverage`.
-
-### Workflow
-
-Here's the most direct way to get your work merged into the project:
-
-- Fork the project.
-- Clone down your fork
-  (`git clone git://github.com/<username>/mime-types-data.git`).
-- Create a topic branch to contain your change
-  (`git checkout -b my\_awesome\_feature`).
-- Hack away, add tests. Not necessarily in that order.
-- Make sure everything still passes by running `rake`.
-- If necessary, rebase your commits into logical chunks, without errors.
-- Push the branch up (`git push origin my\_awesome\_feature`).
-- Create a pull request against mime-types/mime-types-data and describe what
-  your change does and the why you think it should be merged.
-
-## The Release Process
-
-The release process is much more automated than it used to be, as regular
-updates are performed with GitHub actions on Tuesdays. Before release, however,
-a final step of checking for IANA updates should be performed.
-
-1. Review any outstanding issues or pull requests to see if anything needs to be
-   addressed. This is necessary because there is no automated source for
-   extensions for the thousands of MIME entries. (Suggestions and/or pull
-   requests for same would be deeply appreciated.)
-2. `bundle install`
-3. `bundle exec rake mime:apache`
-4. `bundle exec rake mime:iana`
-5. Review the changes to make sure that the changes are sane. The IANA data
-   source changes from time to time, resulting in big changes or even a broken
-   step 4. (The most recent change was the addition of the `font/*` top-level
-   category.)
-6. `bundle exec rake convert`
-7. `bundle exec rake update:version`
-8. Write up the changes in `History.md`. If any PRs have been merged, these
-   should be noted specifically and contributions should be added in
-   `Contributing.md`.
-9. Commit the changes and push to GitHub.
-10. `bundle exec rake release VERSION=newversion`
-
-This is based on an issue [#18][#18].
-
-### Contributors
-
-- Austin Ziegler created mime-types.
-
-Thanks to everyone else who has contributed to mime-types:
-
-- Aaron Patterson
-- Aggelos Avgerinos
-- Alessio Parma
-- Alex Balhatchet
-- Andre Pankratz
-- Andrey Eremin
-- Andy Brody
-- Arnaud Meuret
-- Bradley Meck
-- Brandon Galbraith
-- Chris Gat
-- Chris Salzberg
-- David Genord
-- Eric Marden
-- Garret Alfert
-- Godfrey Chan
-- Greg Brockman
-- Hans de Graaff
-- Henrik Hodne
-- Jeremy Evans
-- John Gardner
-- Jon Sneyers
-- Jonas Petersen
-- Juanito Fatas
-- Keerthi Siva
-- Ken Ip
-- Łukasz Śliwa
-- Lucia
-- Martin d'Allens
-- Mauricio Linhares
-- Mohammed Gad
-- Myk Klemme
-- nycvotes-dev
-- Postmodern
-- Richard Hirner
-- Richard Hurt
-- Richard Schneeman
-- Robert Buchberger
-- Samuel Williams
-- Sergio Baptista
-- Shane Eskritt
-- Tao Guo
-- Thomas Leese
-- Tibor Szolár
-- Todd Carrico
-- Yoran Brondsema
-
-[qcm]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
-[rmt]: https://github.com/mime-types/ruby-mime-types/
-[hoe]: https://github.com/seattlerb/hoe