2026-06-17 Express Working Session

[github-actions]

Date/Time

Timezone	Date/Time
America/Los_Angeles	Wed, Jun 17, 2026, 01:00 PM
America/Denver	Wed, Jun 17, 2026, 02:00 PM
America/Chicago	Wed, Jun 17, 2026, 03:00 PM
America/Bogota	Wed, Jun 17, 2026, 03:00 PM
America/New_York	Wed, Jun 17, 2026, 04:00 PM
UTC	Wed, Jun 17, 2026, 08:00 PM
Europe/London	Wed, Jun 17, 2026, 09:00 PM
Europe/Madrid	Wed, Jun 17, 2026, 10:00 PM
Europe/Paris	Wed, Jun 17, 2026, 10:00 PM
Europe/Warsaw	Wed, Jun 17, 2026, 10:00 PM
Europe/Moscow	Wed, Jun 17, 2026, 11:00 PM
Asia/Kolkata	Thu, Jun 18, 2026, 01:30 AM
Asia/Shanghai	Thu, Jun 18, 2026, 04:00 AM
Asia/Tokyo	Thu, Jun 18, 2026, 05:00 AM
Australia/Sydney	Thu, Jun 18, 2026, 06:00 AM

Or in your local time:

• https://www.timeanddate.com/worldclock/fixedtime.html?msg=2026-06-17%20Express%20Working%20Session&iso=20260617T2000&p1=1440&ah=1

Agenda

Extracted from top priority labelled issues and pull requests from expressjs/discussions prior to the meeting.

• Use Node.js built-in debug and deprecated utilities instead of relying on external packages. #459
• Update the organization logo #426
• Propose a higher minimum Node.js version for all the packages (CI related) #236
• docs: new Collaborator role #486
• docs: update governance to allow long-term contributors to be nominated as committers and captains #485
• docs: update governance document to remove outdated sections #386
• charter: update TC membership guidelines to ensure diverse representation #376
• add Github Access Structure Overview section express#5503

Invited

• @expressjs/express-tc
• @expressjs/triagers
• @expressjs/security-wg

Observers/Guests

This meeting is open for anyone who wants to attend. Reminder to follow our Code of Conduct.

Joining the meeting

• link for participants: https://zoom-lfx.platform.linuxfoundation.org/meeting/95258037175?password=07aad89d-ff43-45df-9b28-f437e167a0b9

---

Please use the following emoji reactions in this post to indicate your
availability.

• 👍 - Attending
• 👎 - Not attending
• 😕 - Not sure yet

[bjohansebas]

Okay, these are some of the things that have been sitting idle and need review from the captains or from the people who blocked them, or they're already ready to be merged, but I can't do that myself

on-finished v3

• https://github.com/jshttp/on-finished/tree/v3 (cc: @wesleytodd @UlisesGascon )
  • feat: add types jshttp/on-finished#69 (cc: @jonchurch because you're blocking it.)
  • feat: support optimizeEmptyRequests node option handling pillarjs/finalhandler#154
    • feat: dump bodies of get/head reqs express#6742

router

• feat: add request layer lifecycle TracingChannels pillarjs/router#196 (cc @wesleytodd @UlisesGascon)

express

• fix: prevent host header injection by sanitizing userinfo in Host header express#7317 (https://github.com/expressjs/express/security/advisories/GHSA-rvrq-qj4c-w73v (It's being blocked to address https://github.com/expressjs/express/security/advisories/GHSA-rvrq-qj4c-w73v, which was closed because it doesn't fit our threat model @expressjs/express-collaborators)
• docs: use the new logo express#7316 (for the new logo in the readme of express cc: @expressjs/express-tc)
• fix: display the correct message when passing a bigint to res.status. express#6758 (cc: @jonchurch because you're blocking it)

send

• chore: bring in the changes from fastify/send pillarjs/send#293 (It looks like Mateo is okay with merging the fork)

on-headers and compression

• new way to pass the configuration to the encodings compression#232 (cc: @UlisesGascon)
• Compression middleware changes behavior of undefined statusText in writeHead compression#254
  • fix: handle undefined statusText in writeHead arguments jshttp/on-headers#49