Skip to content

Backlog for next releases #380

Open
Open

Description

@UlisesGascon

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.

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.

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.

Backlog

We need to plan the release content. These releases are considered blocked until we gain more traction.

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

  1. bjohansebas commented on May 15, 2025

    @bjohansebas
    Member

    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

  2. UlisesGascon commented on May 15, 2025

    @UlisesGascon
    Author
  3. self-assigned this
    on May 15, 2025
  4. bjohansebas commented on May 15, 2025

    @bjohansebas
  5. inidaname commented on May 23, 2025

    @inidaname
  6. bjohansebas commented on May 29, 2025

    @bjohansebas
  7. aqeelat commented on Aug 7, 2025

    @aqeelat

    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.

  8. Phillip9587 commented on Oct 3, 2025

    @Phillip9587
  9. changed the title [-]Backlog for summer releases[/-] [+]Backlog for next releases[/+] on Oct 3, 2025
  10. pinned this issue on Nov 8, 2025
  11. UlisesGascon commented on Nov 17, 2025

    @UlisesGascon
    MemberAuthor

    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 )

  12. bjohansebas commented on Nov 26, 2025

    @bjohansebas
  13. UlisesGascon commented on Nov 26, 2025

    @UlisesGascon
    Author
  14. bjohansebas commented on Jan 9, 2026

    @bjohansebas
    Member

    expressjs/serve-index#144 This falls within my priorities so that webpack-dev-server can migrate to Express 5 without any issues. While there is no problem right now, there could be issues related to the Content-Type.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions