Repository navigation
Backlog for next releases #380
Description
This is the current releases backlog in terms of status and priorities
Important notes:
- The state of the backlog is always reflected in the latest edition of this message.
- Packages and releases are prioritized based on user impact, with security updates and hotfixes considered the most critical.
- Some packages require maintenance releases, as it has been several years since their last update. These items are considered low priority.
- Ideally, each release has a clear leader.
Security Releases (Highest priority)
We intentionally do not disclose more details. This helps us organize the backlog more effectively, as not everyone is aware of which security patches are currently in progress.
- body-parser (repo, npm)
- semver-patch: GHSA-wqch-xfxh-vrr4
- 2.2.1: Release: 2.2.1 body-parser#659
- express (repo, npm)
- semver-minor: GHSA-pj86-cfqh-vqx6
- release: Release: 4.22.0 express#6921
- release: Release: 5.2.0 express#6920
- multiparty (repo, npm)
- semver-minor: GHSA-65x3-rw7q-gx94
This is organized in a specific order to ensure we apply patches on the latest versions. For example, Express depends on body-parser.
High Priority
The community is waiting for these releases, which contain patches and features that we need to ship soon.
- cors (repo, npm)
- Priority: Operational issues with CORS cors#346
- Lead: @UlisesGascon / @efekrskl
- compressible (repo, npm):
- Proposal 2.0.19: Release: 2.0.19 jshttp/compressible#32
- Lead: @UlisesGascon
- on-finished (repo, npm):
- semver-major: Release Proposal: on-finished@3.0.0 jshttp/on-finished#57
- Lead: @Phillip9587 / @UlisesGascon
- mime-db (repo, npm):
- Backlog: Backlog for Release 1.55.0 jshttp/mime-db#414
- Create a release proposal PR
- Lead: @UlisesGascon
- iconv-lite (repo, npm):
- Release: release: 0.7.1 pillarjs/iconv-lite#359
- Release: 1.x (TBC)
- Lead: @bjohansebas
- content-disposition (repo, npm):
- Proposal 1.0.1: Release: 1.0.1 jshttp/content-disposition#58
- Lead: @Phillip9587 / @UlisesGascon
- mime-types (repo, npm):
- Proposal 3.0.2 Release: 3.0.2 jshttp/mime-types#169
- Lead: @UlisesGascon
- http-errors (repo, npm):
- Motivation: This would deduplicate the
statusespackage in our dependency tree: npm graph - Proposal 2.0.1 Release: 2.0.1 jshttp/http-errors#140
- Lead: @UlisesGascon
- Motivation: This would deduplicate the
- serve-static (repo, npm)
- Lead: @UlisesGascon
- Priority: deps: send@~0.19.1 serve-static#227
- Release: Release: 2.2.1 serve-static#228
- Release: Release: 1.16.3 serve-static#229
- send (repo, npm)
- finalhandler (repo, npm)
- body-parser (repo, npm)
- cookie (repo, npm)
- Lead: @blakeembrey
cookie@1.1.0: https://github.com/jshttp/cookie/releases/tag/v1.1.0
Medium Priority
The community is waiting for these releases, which include patches and features that we can release without urgency. In some cases, the release backlog is not yet ready.
- multer (repo, npm):
- semver-major and semver-patch pending: Releases Backlog (2.1.0 and 3.0.0) multer#1310
- Lead: @bjohansebas / @UlisesGascon / @LinusU
- compression (repo, npm):
- semver-major: Compression v2 compression#234
- Lead: @bjohansebas / @UlisesGascon
- express-session (repo, npm):
- semver-major: backlog for express-session@2.x session#1006
- Lead: @UlisesGascon / @bjohansebas
- response-time (repo, npm)
- basic-auth-connect (repo, npm):
- semver-major: Backlog: Release v2.0 basic-auth-connect#8
- Lead: @UlisesGascon
- hbs (repo, npm)
- semver-major: https://github.com/pillarjs/hbs/tree/5.0
- Lead: @UlisesGascon / @mfdebian
- on-headers (repo, npm):
- semver-major: on-headers v2 jshttp/on-headers#18
- Lead: @bjohansebas / @UlisesGascon
- content-type (repo, npm):
- semver-major: v2.0.0 - Major Release (Proposal) jshttp/content-type#27
- Lead: @Phillip9587 / @UlisesGascon
- basic-auth (repo, npm):
- semver-major:
basic-authv3 - Proposal jshttp/basic-auth#70 - Lead: @Phillip9587 / @UlisesGascon
- semver-major:
- errorhandler (repo, npm)
- Lead: @UlisesGascon / @nanotower
- cookies (repo, npm)
- semver-major proposal: 1.0.0 pillarjs/cookies#48
- Lead: @UlisesGascon / @imangas
- http-assert (repo, npm)
- Motivation: Update
http-errorsto v2 jshttp/http-assert#37 - Lead: @UlisesGascon
- Motivation: Update
Backlog
We need to plan the release content. These releases are considered blocked until we gain more traction.
- serve-index (repo, npm)
- method-override (repo, npm)
- vhost (repo, npm)
- parseurl (repo, npm)
- csrf (repo, npm)
- resolve-path (repo, npm)
- media-typer (repo, npm)
- vary (repo, npm)
- methods (repo, npm)
- range-parser (repo, npm)
- proxy-addr (repo, npm)
- etag (repo, npm)
- http-errors (repo, npm)
- forwarded (repo, npm)
- semver-major proposal: v1.0.0-rc.1 jshttp/forwarded#1
On hold
We released a version recently, but we can prepare a new one containing the remaining open issues, dependency upgrades, and other improvements.
Activity
bjohansebas commentedon May 15, 2025
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 commentedon May 15, 2025
bjohansebas commentedon May 15, 2025
inidaname commentedon May 23, 2025
bjohansebas commentedon May 29, 2025
aqeelat commentedon Aug 7, 2025
I would like to help cut releases for some of these packages (esp ones under jshttp). I know I don't have credibility with the expressjs maintainers; how can I get involved?
From a quick glance, most of the changes needed are dependency upgrades.
I can also help create an nx monorepo and help core devs migrate the packages to it.
Phillip9587 commentedon Oct 3, 2025
[-]Backlog for summer releases[/-][+]Backlog for next releases[/+]UlisesGascon commentedon Nov 17, 2025
I just updated the main issue with the current backlog (cc: @bjohansebas @Phillip9587 @carpasse @mfdebian )
#380 (comment)
If you see something that does not make sense, or you want to delegate some work let me know here or in slack 👍
I hope this finally makes more clear where we are and what is going to happen next. I also included a mention to the future security releases so it is easier to plan also outside of the @expressjs/security-triage (cc: @expressjs/express-tc )
bjohansebas commentedon Nov 26, 2025
UlisesGascon commentedon Nov 26, 2025
bjohansebas commentedon Dec 29, 2025
pillarjs/iconv-lite#370
https://github.com/expressjs/session/milestone/3
bjohansebas commentedon Jan 9, 2026
expressjs/serve-index#144 This falls within my priorities so that
webpack-dev-servercan migrate to Express 5 without any issues. While there is no problem right now, there could be issues related to theContent-Type.