Skip to content

fix(deps): update dependency express to v5 - #119

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/express-5.x
Open

fix(deps): update dependency express to v5#119
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/express-5.x

Conversation

@renovate

@renovate renovate Bot commented Mar 31, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
express (source) ^4.14.0^5.0.0 age confidence

Release Notes

expressjs/express (express)

v5.2.1

Compare Source

=======================

  • Revert security fix for CVE-2024-51999 (GHSA-pj86-cfqh-vqx6)
    • The prior release (5.2.0) included an erroneous breaking change related to the extended query parser. There is no actual security vulnerability associated with this behavior (CVE-2024-51999 has been rejected). The change has been fully reverted in this release.

v5.2.0

Compare Source

========================

  • Security fix for CVE-2024-51999 (GHSA-pj86-cfqh-vqx6)
  • deps: body-parser@^2.2.1
  • A deprecation warning was added when using res.redirect with undefined arguments, Express now emits a warning to help detect calls that pass undefined as the status or URL and make them easier to fix.

v5.1.0

Compare Source

========================

  • Add support for Uint8Array in res.send()
  • Add support for ETag option in res.sendFile()
  • Add support for multiple links with the same rel in res.links()
  • Add funding field to package.json
  • perf: use loop for acceptParams
  • refactor: prefix built-in node module imports
  • deps: remove setprototypeof
  • deps: remove safe-buffer
  • deps: remove utils-merge
  • deps: remove methods
  • deps: remove depd
  • deps: debug@^4.4.0
  • deps: body-parser@^2.2.0
  • deps: router@^2.2.0
  • deps: content-type@^1.0.5
  • deps: finalhandler@^2.1.0
  • deps: qs@^6.14.0
  • deps: server-static@2.2.0
  • deps: type-is@2.0.1

v5.0.1

Compare Source

==========

v5.0.0

Compare Source

=========================

  • remove:
    • path-is-absolute dependency - use path.isAbsolute instead
  • 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: send@​1.0.0
    • res.redirect('back') and res.location('back') is no longer a supported magic string, explicitly use req.get('Referrer') || '/'.
  • change:
    • res.clearCookie will ignore user provided maxAge and expires options
  • deps: cookie-signature@^1.2.1
  • deps: debug@​4.3.6
  • deps: merge-descriptors@^2.0.0
  • deps: serve-static@^2.1.0
  • deps: qs@​6.13.0
  • 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

v4.22.2

Compare Source

What's Changed

  • fix: restore >20 array parsing for req.query repeated keys (8d09bfe6)
    • This also unifies array-cap behavior across notations. Indexed notation (a[0]=...) was historically capped at qs's default arrayLimit of 20 even in older qs versions; after this change it also allows up to 1000 items.
  • deps: qs@~6.15.1
  • deps: body-parser@~1.20.5

New Contributors

Full Changelog: expressjs/express@v4.22.1...v4.22.2

v4.22.1

Compare Source

What's Changed

[!IMPORTANT]
The prior release (4.22.0) included an erroneous breaking change related to the extended query parser. There is no actual security vulnerability associated with this behavior (CVE-2024-51999 has been rejected). The change has been fully reverted in this release.

Full Changelog: expressjs/express@4.22.0...v4.22.1

v4.22.0

Compare Source

Important: Security

What's Changed

Full Changelog: expressjs/express@4.21.2...4.22.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/express-5.x branch from 3517d07 to 2159573 Compare August 10, 2025 14:22
@renovate
renovate Bot force-pushed the renovate/express-5.x branch from 2159573 to 4eb4698 Compare September 25, 2025 14:03
@renovate
renovate Bot force-pushed the renovate/express-5.x branch 2 times, most recently from e117256 to 8526488 Compare December 2, 2025 02:56
@renovate
renovate Bot force-pushed the renovate/express-5.x branch from 8526488 to 08af06c Compare December 31, 2025 16:56
@renovate
renovate Bot force-pushed the renovate/express-5.x branch from 08af06c to b4fa776 Compare January 8, 2026 18:50
@renovate
renovate Bot force-pushed the renovate/express-5.x branch 2 times, most recently from 7d321ec to e36de2b Compare February 17, 2026 17:07
@renovate
renovate Bot force-pushed the renovate/express-5.x branch from e36de2b to b32ddef Compare April 16, 2026 02:42
@renovate
renovate Bot force-pushed the renovate/express-5.x branch from b32ddef to 9f3a72c Compare May 18, 2026 12:05
@renovate
renovate Bot force-pushed the renovate/express-5.x branch from 9f3a72c to 1c73e71 Compare June 14, 2026 20:06
@renovate
renovate Bot force-pushed the renovate/express-5.x branch from 1c73e71 to 13ee855 Compare July 12, 2026 19:13
@renovate
renovate Bot force-pushed the renovate/express-5.x branch from 13ee855 to bf80e5d Compare July 24, 2026 20:17
@renovate
renovate Bot force-pushed the renovate/express-5.x branch from bf80e5d to 2d4408c Compare August 14, 2026 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants