MIME Types Changes by Version

3.2026.0113 / 2026-01-13

3.2026.0106 / 2026-01-06

3.2025.0924 / 2025-09-24

3.2025.0916 / 2025-09-16

3.2025.0909 / 2025-09-09

3.2025.0902 / 2025-09-02

3.2025.0826 / 2025-08-26

3.2025.0819 / 2025-08-19

3.2025.0812 / 2025-08-12

3.2025.0805 / 2025-08-05

3.2025.0729 / 2025-07-29

The logic is three relatively simple phases:

  1. When loading an existing registry grouping (such as types/application.yaml), we mark any type that is provisional as obsolete. This indicates that we consider any provisional type as potentially withdrawn (and therefore obsolete).

  2. When processing existing regular types, we clear both provisional and obsolete flags so that a type promoted from provisional is now a regular registry entry.

  3. After merging the current list of registry entries, we clear provisional if the type is marked both provisional and obsolete, indicating that the provisional type has been withdrawn.

These heuristics match several types which have been promoted and withdrawn since the handling of provisional types was improved with #53.

3.2025.0722 / 2025-07-22

3.2025.0715 / 2025-07-15

3.2025.0708 / 2025-07-08

3.2025.0701 / 2025-07-01

3.2025.0624 / 2025-06-24

3.2025.0617 / 2025-06-17

3.2025.0610 / 2025-06-10

3.2025.0603 / 2025-06-03

3.2025.0527 / 2025-05-27

3.2025.0520 / 2025-05-20

3.2025.0514 / 2025-05-14

3.2025.0507 / 2025-05-07

3.2025.0506 / 2025-05-06

3.2025.0429 / 2025-04-29

3.2025.0422 / 2025-04-22

3.2025.0408 / 2025-04-08

3.2025.0402 / 2025-04-02

3.2025.0325 / 2025-03-25

3.2025.0318 / 2025-03-18

3.2025.0304 / 2025-03-04

3.2025.0220 / 2025-02-20

3.2025.0204 / 2025-02-04

3.2025.0107 / 2025-01-07

3.2024.1203 / 2024-12-03

3.2024.1105 / 2024-11-05

3.2024.1001 / 2024-10-01

3.2024.0903 / 2024-09-03

3.2024.0820 / 2024-08-20

3.2024.0806 / 2024-08-06

3.2024.0702 / 2024-07-02

3.2024.0604 / 2024-06-04

3.2024.0507 / 2024-05-07

3.2024.0402 / 2024-04-02

3.2024.0305 / 2024-03-05

3.2024.0206 / 2024-02-06

3.2024.0102 / 2024-01-02

3.2023.1205 / 2023-12-05

3.2023.1107 / 2023-11-07

3.2023.1003 / 2023-10-03

3.2023.0905 / 2023-09-05

3.2023.0808 / 2023-08-08

3.2023.0218.1 / 2023-02-18

A hot fix has been applied to resolve this. However, note that application/javascript will not be returned by default, only text/javascript.

3.2023.0218 / 2023-02-18

It is worth noting that this is an imperfect solution as if a media type is provisionally registered and withdrawn, it will linger in the registry with no clean way of identifying them at the moment. See #54.

This release also fixes ruby-mime-types#163, where logs show “Type application/netcdf is already registered as a variant of application/netcdf”.

3.2022.0105 / 2022-01-05

3.2021.1115 / 2021-11-15

3.2021.0901 / 2021-09-01

3.2021.0704 / 2021-07-04

3.2021.0225 / 2021-02-25

3.2021.0212 / 2021-02-12

3.2020.1104 / 2020-11-04

3.2020.0512 / 2020-05-12

3.2020.0425 / 2020-04-25

3.2019.1009 / 2019-10-09

3.2019.0904 / 2019-09-04

3.2019.0331 / 2019-03-31

3.2018.0812 / 2018-08-12

3.2016.0521 / 2016-05-21

3.2016.0221 / 2016-02-21

3.2015.1120 / 2015-11-20

2.6.2 / 2015-09-13

2.6 / 2015-05-25

2.5 / 2015-04-25

2.4.2 / 2014-10-15

2.4.1 / 2014-10-07

2.3 / 2014-05-23

2.2 / 2014-03-14

2.1 / 2014-01-25