Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2025-03-31 Express TC Meeting #351

Closed
github-actions bot opened this issue Mar 25, 2025 · 2 comments
Closed

2025-03-31 Express TC Meeting #351

github-actions bot opened this issue Mar 25, 2025 · 2 comments
Labels

Comments

@github-actions
Copy link

github-actions bot commented Mar 25, 2025

Date/Time

Timezone Date/Time
America/Los_Angeles Mon 31-Mar-2025 14:00 (02:00 PM)
America/Denver Mon 31-Mar-2025 15:00 (03:00 PM)
America/Chicago Mon 31-Mar-2025 16:00 (04:00 PM)
America/New_York Mon 31-Mar-2025 17:00 (05:00 PM)
Europe/London Mon 31-Mar-2025 22:00 (10:00 PM)
Europe/Amsterdam Mon 31-Mar-2025 23:00 (11:00 PM)
Europe/Moscow Tue 01-Apr-2025 00:00 (12:00 AM)
Asia/Kolkata Tue 01-Apr-2025 02:30 (02:30 AM)
Asia/Shanghai Tue 01-Apr-2025 05:00 (05:00 AM)
Asia/Tokyo Tue 01-Apr-2025 06:00 (06:00 AM)
Australia/Sydney Tue 01-Apr-2025 08:00 (08:00 AM)

Or in your local time:

Agenda

Extracted from tc agenda labelled issues and pull requests from expressjs/discussions prior to the meeting.

Invited

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

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

Links

  • Minutes:

Joining the meeting

@jonchurch
Copy link
Member

jonchurch commented Mar 31, 2025

What about this for messaging on the EOL?

📢 Express v5 is now ACTIVE — What That Means for You

We’re excited to announce that Express v5 has officially moved into ACTIVE support! 🎉

This marks a big milestone for the project — thank you to everyone who contributed, tested, and gave feedback throughout the v5 release cycle.


What’s Changing Now?

  • v5 is now the recommended version: It is tagged latest on npm and will receive all active updates, including bug fixes, security patches, new features, and deprecation notices.
  • v4 has entered MAINTENANCE: It will continue receiving critical security and high-priority bug fixes only.

What About EOL for v4?

We don’t have a fixed end-of-life (EOL) date for v4 yet. Here’s why:

Under our new Long Term Support (LTS) strategy, a major version moves from ACTIVE to MAINTENANCE when the next major version becomes ACTIVE. That’s what just happened: with Express v5 now ACTIVE, Express v4 has entered MAINTENANCE.

  • A version typically stays in MAINTENANCE for at least 12 months, but v4 is a special case due to its long history and wide usage.
  • The final EOL date for v4 will depend on when Express v6 is released, and that timeline hasn’t been set yet.

So: you can continue using v4 safely during this maintenance window, but we recommend starting to plan your upgrade to v5.

We’ll communicate early and clearly as plans for v6 evolve and the v4 EOL window becomes more concrete.


Chris called out that this isn't accurate:

The final EOL date for v4 will depend on when Express v6 is released ...

@jonchurch
Copy link
Member

Ulises requested review on these two Security WG related PRs 🙏
expressjs/security-wg#56
expressjs/.github#15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants