chore(deps): bump the major-dependencies group across 1 directory with 3 updates

[dependabot]

Bumps the major-dependencies group with 3 updates in the / directory: express, @types/express and openid-client.

Updates express from 4.21.0 to 5.0.1

Release notes

Sourced from express's releases.

5.0.1

What's Changed

• remove --bail from test script by @​jonchurch in expressjs/express#5962
• Nominate @​bjohansebas to the triage team by @​UlisesGascon in expressjs/express#6009
• Link and update captains by @​blakeembrey in expressjs/express#6013
• Update cookie semver lock to address CVE-2024-47764 by @​joshbuker in expressjs/express#6017
• Release: 5.0.1 by @​UlisesGascon in expressjs/express#6032

Full Changelog: expressjs/express@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-parser changes: Several improvements including the ability to customize urlencoded body depth and defaulting extended to false.
• 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 @​wesleytodd in expressjs/express#5561
• remove duplicate location test for data uri by @​wesleytodd in expressjs/express#5562
• feat: document beta releases expectations by @​marco-ippolito in expressjs/express#5565
• Cut down on duplicated CI runs by @​jonchurch in expressjs/express#5564

... (truncated)

Changelog

Sourced from express's changelog.

5.0.1 / 2024-10-08

• Update cookie semver lock to address CVE-2024-47764

5.0.0 / 2024-09-10

• 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: [email protected]
  • 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: [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

• d14b2de 5.0.1
• 2027b87 fix(deps): [email protected]
• 2cbf227 Link and update captains (#6013)
• 3e1a1ce Add @​bjohansebas to the triage team (#6009)
• 6340d15 remove --bail from test script (#5962)
• 344b022 5.0.0
• 0c49926 fix(deps): send@^1.1.0
• b3906cb fix(deps): serve-static@^2.1.0
• fed8c2a fix(deps): body-parser@^2.0.1
• bdd81f8 Delete back as a magic string (#5933)
• Additional commits viewable in compare view

Updates @types/express from 4.17.21 to 5.0.0

Commits

• See full diff in compare view

Updates openid-client from 5.7.0 to 6.1.3

Release notes

Sourced from openid-client's releases.

v6.1.3

Documentation

• remove note from issuer transformation algorithm (5fda2cb)

Fixes

• deal with discovery issues from b2clogin.com (b9a4f2f), closes #718

v6.1.2

Refactor

• rename the parameters positional argument in authorizationCodeGrant() (c79ccc5), closes #712

Documentation

• document behaviour of customFetch on discovery (072da62)
• update Strategy.prototype.currentUrl JSDoc (46ea086), closes #714

v6.1.1

Documentation

• update link to passport example (110575b)

Fixes

• correct supportsPKCE bool return (f1aa9db), closes #710

v6.1.0

Features

• add a server metadata helper for checking PKCE support (ca34a91)
• add JWKS Cache management for use in non-persistent runtimes (cda4b53)

v6.0.0

⚠ BREAKING CHANGES

• openid-client v6.x is a complete rewrite of the openid-client module, this is the first time since 0.1.0 (8 years ago) that the API has drastically changed. The new module structure and API focuses on three core principles:

• runtime compatibility (adding support for Deno, Cloudflare Workers, Bun, and other Web API interoperable runtimes)
• tree-shakeability (bundles should not contain features that don't end up being used)
• less options (removing support for processing deprecated response types, cutting down on the number of combinations that need to handled)

To that end openid-client@6 no longer supports the full cartesian matrix of response types and response modes, it no longer supports issuing encrypted assertions, decrypting assertions is limited to only a few algorithms, it no longer supports Dynamic Client Registration or Management, and Self-Issued OpenID Provider responses are also not supported.

The new API makes basic setups simple while allowing some degree of complexity where needed.

... (truncated)

Changelog

Sourced from openid-client's changelog.

6.1.3 (2024-10-23)

Documentation

• remove note from issuer transformation algorithm (5fda2cb)

Fixes

• deal with discovery issues from b2clogin.com (b9a4f2f), closes #718

6.1.2 (2024-10-23)

Refactor

• rename the parameters positional argument in authorizationCodeGrant() (c79ccc5), closes #712

Documentation

• document behaviour of customFetch on discovery (072da62)
• update Strategy.prototype.currentUrl JSDoc (46ea086), closes #714

6.1.1 (2024-10-18)

Documentation

• update link to passport example (110575b)

Fixes

• correct supportsPKCE bool return (f1aa9db), closes #710

6.1.0 (2024-10-17)

Features

• add a server metadata helper for checking PKCE support (ca34a91)
• add JWKS Cache management for use in non-persistent runtimes (cda4b53)

6.0.0 (2024-10-15)

⚠ BREAKING CHANGES

... (truncated)

Commits

• 2cca13a chore(release): 6.1.3
• cd5e7d7 test: add a test for ensuring 30x non-conform behaviours can be worked around
• b9a4f2f fix: deal with discovery issues from b2clogin.com
• 5fda2cb docs: remove note from issuer transformation algorithm
• 2fe2496 test: add regression test for issue 704
• c7fb6e4 chore: cleanup after release
• e67cc23 chore(release): 6.1.2
• 46ea086 docs: update Strategy.prototype.currentUrl JSDoc
• b0e57fe chore: update README.md
• 3e0adf6 chore: bump deps
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions