Backlog for summer releases

[UlisesGascon]

Some packages require some work to be done in order to make proper releases, I plan to work on this in the following weeks. I will include specific issues with the release proposals, backlog, etc... But we can centralize discussions here.

In Scope

• multer (repo, npm):
  • 2.0.0 (sec release): https://github.com/expressjs/multer/releases/tag/v2.0.0
  • 3.0.0-alpha.1: Release: v3.0.0-alpha.1  multer#1320
  • Normalize the repo branches and versions multer#1313
  • 2.0.1 (sec release): https://github.com/expressjs/multer/releases/tag/v2.0.1
  • 3.0.0: Releases Backlog (2.1.0 and 3.0.0) multer#1310
  • 2.1.0: Releases Backlog (2.1.0 and 3.0.0) multer#1310
• compression (repo, npm): Compression v2 compression#234
• express-session (repo, npm): backlog for express-session@2.x session#1006
• serve-index (repo, npm): Release 1.10.0
• method-override (repo, npm): release 3.1.0
• serve-favicon (repo, npm):
  • 2.5.1 Release: 2.5.1 serve-favicon#68
• response-time (repo, npm): Release 3.0.0 (Discussion: Proposed Changes for expressjs/response-time Next Major Version response-time#25)
• cors (repo, npm): Release 3.0.0 or 2.9.0
• morgan (repo, npm): Release 1.11.0
• errorhandler (repo, npm): Release 1.6.0
• basic-auth-connect (repo, npm): Backlog: Release v2.0 basic-auth-connect#8
• vhost (repo, npm): Release 3.1.0
• connect-timeout (repo, npm): Release 1.10.0
• cookies (repo, npm): 1.0.0 pillarjs/cookies#48
• parseurl (repo, npm): Release 1.4.0
• csrf (repo, npm): Release 3.2.0
• multiparty (repo, npm): Release 4.3.0
• hbs (repo, npm): Release 4.3.0
• resolve-path (repo, npm): Release 1.5.0
• compressible (repo, npm):
  • 2.0.19 Release: 2.0.19 jshttp/compressible#32
• media-typer (repo, npm): Release 1.2.0
• vary (repo, npm): Release 1.2.0
• methods (repo, npm): Release 1.2.0
• on-headers (repo, npm): on-headers v2 jshttp/on-headers#18
• range-parser (repo, npm): Release 1.3.0
• proxy-addr (repo, npm): Release 2.1.0
• http-assert (repo, npm): Release 1.6.0
• content-type (repo, npm): v2.0.0 - Major Release (Proposal) jshttp/content-type#27
• etag (repo, npm): Release 1.9.0
• basic-auth (repo, npm): basic-auth v3 - Proposal jshttp/basic-auth#70
• http-errors (repo, npm): Release 2.1.0
• statuses (repo, npm):
  • 2.0.2: Release: 2.0.2 jshttp/statuses#40
• forwarded (repo, npm): v1.0.0-rc.1 jshttp/forwarded#1
• content-disposition (repo, npm): Release: 1.0.1 jshttp/content-disposition#58
• on-finished (repo, npm): Release Proposal: on-finished@3.0.0 jshttp/on-finished#57

Important

• Note that I suggest all the changes as at least minor version. Some of the minor ones might end up being patch.
• This list is a draft, so expect changes in packages and versions

[bjohansebas]

For multer@2 mainly, it remains to switch to CommonJS, update the dependencies, and move support to Node >=18

compression@2 while some PRs have been reviewed, the main one is still not finished (expressjs/compression#183). If anyone can help us, that would be great. A beta will be launched when (expressjs/compression#153 and expressjs/compression#232) are merged.

on-finished@3 I’m going to work on HTTP2 support, since this will also depend on compression@2 and the goal of releasing Express v6 with HTTP2.

on-headers I think we’re going to release a new major version, dropping support for the old Node.js versions and adding support for HTTP2, which is also essential for compression@2

I think I’m not forgetting anything else from the packages I’m working on or that depend on my changes

[UlisesGascon]

@bjohansebas can you create the backlog issues for multer@2 and compression@2? Thanks for taking the leaderhip ❤️

[bjohansebas]

compression v2: expressjs/compression#234
multer v2: expressjs/multer#1310
on-headers v2: jshttp/on-headers#18

[inidaname]

For a new Express contributor, how would one go about helping out here?

[bjohansebas]

Hi @inidaname! We have this guide for doing triage in the repositories. I recommend you pick a repository and take a look at the existing issues, or check out the current PRs