Bump express from 4.21.1 to 5.0.1
Bumps express from 4.21.1 to 5.0.1.
Release notes
Sourced from express's releases.
5.0.1
What's Changed
- remove --bail from test script by
@jonchurchin expressjs/express#5962- Nominate
@bjohansebasto the triage team by@UlisesGasconin expressjs/express#6009- Link and update captains by
@blakeembreyin expressjs/express#6013- Update
cookiesemver lock to address CVE-2024-47764 by@joshbukerin expressjs/express#6017- Release: 5.0.1 by
@UlisesGasconin expressjs/express#6032Full Changelog: https://github.com/expressjs/express/compare/v5.0.0...5.0.1
5.0.0
Express v5.0.0
🎉 Express v5 is finally here! 🎉
After years of development, the long-awaited Express v5 has been officially released. This version focuses on simplifying the codebase, improving security, and dropping support for older Node.js versions to enable better performance and maintainability.
For detailed information, please check out the official Express v5 release blog post.
Most relevant details
Major Changes in v5
- Node.js version support: Dropped support for Node.js versions before v18.
- Routing changes: Updated to
[email protected], removing sub-expression regex patterns for security reasons (ReDoS mitigation).- Promise support: Middleware can now return rejected promises, caught by the router as errors.
body-parserchanges: Several improvements including the ability to customizeurlencodedbody depth and defaultingextendedtofalse.- Deprecated API methods removed: Removed old, deprecated API method signatures from Express v3/v4.
For a complete list of breaking changes and API deprecations, see the migration guide.
Security Updates
This release includes important security fixes, including improvements to prevent ReDoS attacks and mitigation for CVE-2024-45590. Full details can be found in the security release notes.
Migration
Be sure to check out our migration guide for instructions on how to update your applications from Express v4 to v5.
Security Guidance
For best practices, we recommend reviewing the Threat Model which outlines Express' approach to securing your applications, including tips for user input validation and other critical aspects.
What's Changed
- 4.19.2 Staging by
@wesleytoddin expressjs/express#5561- remove duplicate location test for data uri by
@wesleytoddin expressjs/express#5562- feat: document beta releases expectations by
@marco-ippolitoin expressjs/express#5565- Cut down on duplicated CI runs by
@jonchurchin expressjs/express#5564
... (truncated)
Changelog
Sourced from express's changelog.
5.0.1 / 2024-10-08
- Update
cookiesemver lock to address CVE-2024-477645.0.0 / 2024-09-10
- remove:
path-is-absolutedependency - usepath.isAbsoluteinstead- breaking:
res.status()accepts only integers, and input must be greater than 99 and less than 1000
- will throw a
RangeError: Invalid status code: ${code}. Status code must be greater than 99 and less than 1000.for inputs outside this range- will throw a
TypeError: Invalid status code: ${code}. Status code must be an integer.for non integer inputs- deps: [email protected]
res.redirect('back')andres.location('back')is no longer a supported magic string, explicitly usereq.get('Referrer') || '/'.- change:
res.clearCookiewill ignore user providedmaxAgeandexpiresoptions- deps: cookie-signature@^1.2.1
- deps: [email protected]
- deps: merge-descriptors@^2.0.0
- deps: serve-static@^2.1.0
- deps: [email protected]
- deps: accepts@^2.0.0
- deps: mime-types@^3.0.0
application/javascript=>text/javascript- deps: type-is@^2.0.0
- deps: content-disposition@^1.0.0
- deps: finalhandler@^2.0.0
- deps: fresh@^2.0.0
- deps: body-parser@^2.0.1
- deps: send@^1.1.0
5.0.0-beta.3 / 2024-03-25
This incorporates all changes after 4.19.1 up to 4.19.2.
5.0.0-beta.2 / 2024-03-20
This incorporates all changes after 4.17.2 up to 4.19.1.
5.0.0-beta.1 / 2022-02-14
This is the first Express 5.0 beta release, based off 4.17.2 and includes changes from 5.0.0-alpha.8.
- change:
- Default "query parser" setting to
'simple'
... (truncated)
Commits
d14b2de5.0.12027b87fix(deps): [email protected]2cbf227Link and update captains (#6013)3e1a1ceAdd@bjohansebasto the triage team (#6009)6340d15remove --bail from test script (#5962)344b0225.0.00c49926fix(deps): send@^1.1.0b3906cbfix(deps): serve-static@^2.1.0fed8c2afix(deps): body-parser@^2.0.1bdd81f8Deletebackas a magic string (#5933)- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
@dependabot rebase
Waiting for 2025-05-01, when this package will also drop support for Node.js 14, 16 and 18.
Superseded by #100.