-
Notifications
You must be signed in to change notification settings - Fork 18
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
Comments
What about this for messaging on the EOL? 📢 Express v5 is now ACTIVE — What That Means for YouWe’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?
What About EOL for v4?We don’t have a fixed end-of-life (EOL) date for v4 yet. Here’s why:
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:
|
Ulises requested review on these two Security WG related PRs 🙏 |
Date/Time
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
Joining the meeting
The text was updated successfully, but these errors were encountered: