Skip to content

Conversation

@bjohansebas
Copy link
Member

@bjohansebas bjohansebas commented Jan 9, 2026

What's included in the HISTORY.md

  * Fix icons for MIME types with `+`
  * Fix text and json responses to match html sorting
  * Show font icon for more font types
  * Use 400 error on URI decode failure instead of 500
  * deps: accepts@~1.3.8
    - deps: mime-types@~2.1.24
    - deps: [email protected]
  * deps: http-errors@~1.8.0
    - Set constructor name when possible
    - deps: depd@~1.1.2
    - deps: [email protected]
    - deps: [email protected]
    - deps: statuses@'>= 1.5.0 < 2'
  * deps: mime-types@~2.1.35
    - Add new mime types
    - deps: mime-db@~1.52.0
  * deps: parseurl@~1.3.3

What's Changed

This will be included in the release details

🐞 Bug fixes

  • Icons for MIME types containing "+" were not displayed correctly - by @dougwilson in 4e7785c

    fixed where file icons with MIME types containing the "+" character (such as image/svg+xml) were not displayed correctly. The bug occurred during the conversion of the MIME type to a CSS class name, since the "+" symbol is not valid in class names.

  • Improved error handling for malformed URIs by @rjoonas in #85

    The HTTP response status code has been fixed for cases where the server receives a URI that cannot be properly decoded. It now returns a 400 (Bad Request) error instead of a 500 (Internal Server Error), more accurately reflecting that the issue is with the client’s request rather than the server itself.

🚀 Improvements

  • Sorting in text/plain and application/json responses by @dougwilson in 002a251

  • Show font icon for more font types - by @dougwilson in 9d29665

    Support has been expanded to display the font icon in directory listings. Now all font file formats will automatically show the corresponding icon, instead of only a few specific formats as before.

PRs

New Contributors

Full Changelog: v1.9.1...master

@bjohansebas
Copy link
Member Author

i will do the rebase once #147 is merge

@bjohansebas bjohansebas requested review from UlisesGascon and blakeembrey and removed request for blakeembrey January 12, 2026 15:37
@bjohansebas
Copy link
Member Author

cc: @expressjs/express-tc

@UlisesGascon UlisesGascon self-assigned this Jan 12, 2026
Copy link
Member

@UlisesGascon UlisesGascon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I plan to do a release this week, but we need to decide first between #149 or #142. How urgent do you need the release @bjohansebas? Worse case scenario I can do a local publication release to unblock u.

@bjohansebas
Copy link
Member Author

Actually, this release is to unblock #144 so we can make changes to update libraries.

@bjohansebas
Copy link
Member Author

While that’s happening, can you create the new branch, or would you like me to do it on master?

@UlisesGascon
Copy link
Member

Created v2.x. I will pull this commit later on to that branch. Feel free to work against the branch. We can try to release both versions on Thursday 🤔

@UlisesGascon UlisesGascon merged commit e754480 into expressjs:master Jan 22, 2026
32 checks passed
@bjohansebas bjohansebas deleted the release-1.9.2 branch January 22, 2026 14:51
UlisesGascon added a commit that referenced this pull request Jan 22, 2026
Co-authored-by: Ulises Gascón <[email protected]>
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.

2 participants