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

Update dependency body-parser to v1.20.2 #64

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 22, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
body-parser 1.19.0 -> 1.20.2 age adoption passing confidence

Release Notes

expressjs/body-parser (body-parser)

v1.20.2

Compare Source

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

  • Fix strict json error message on Node.js 19+
  • deps: content-type@~1.0.5
    • perf: skip value escaping when unnecessary
  • deps: raw-body@2.5.2

v1.20.1

Compare Source

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

  • deps: qs@6.11.0
  • perf: remove unnecessary object clone

v1.20.0

Compare Source

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

  • Fix error message for json parse whitespace in strict
  • Fix internal error when inflated body exceeds limit
  • Prevent loss of async hooks context
  • Prevent hanging when request already read
  • deps: depd@2.0.0
    • Replace internal eval usage with Function constructor
    • Use instance methods on process to check for listeners
  • deps: http-errors@2.0.0
    • deps: depd@2.0.0
    • deps: statuses@2.0.1
  • deps: on-finished@2.4.1
  • deps: qs@6.10.3
  • deps: raw-body@2.5.1
    • deps: http-errors@2.0.0

v1.19.2

Compare Source

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

  • deps: bytes@3.1.2
  • deps: qs@6.9.7
    • Fix handling of __proto__ keys
  • deps: raw-body@2.4.3
    • deps: bytes@3.1.2

v1.19.1

Compare Source

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

  • deps: bytes@3.1.1
  • deps: http-errors@1.8.1
    • deps: inherits@2.0.4
    • deps: toidentifier@1.0.1
    • deps: setprototypeof@1.2.0
  • deps: qs@6.9.6
  • deps: raw-body@2.4.2
    • deps: bytes@3.1.1
    • deps: http-errors@1.8.1
  • deps: safe-buffer@5.2.1
  • deps: type-is@~1.6.18

Configuration

📅 Schedule: 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/body-parser-1.x-lockfile branch from fd302f6 to ec9b10c Compare May 29, 2023 23:57
@renovate renovate bot force-pushed the renovate/body-parser-1.x-lockfile branch from ec9b10c to 5c41014 Compare July 19, 2023 17:40
@renovate renovate bot force-pushed the renovate/body-parser-1.x-lockfile branch from 5c41014 to 00e0e56 Compare August 9, 2023 23:55
@renovate renovate bot force-pushed the renovate/body-parser-1.x-lockfile branch 2 times, most recently from af1632a to a6edde7 Compare October 16, 2023 05:40
@renovate renovate bot force-pushed the renovate/body-parser-1.x-lockfile branch from a6edde7 to 29aaa89 Compare October 24, 2023 11:56
@renovate renovate bot force-pushed the renovate/body-parser-1.x-lockfile branch from 29aaa89 to 93c3e95 Compare December 3, 2023 08:52
@renovate renovate bot force-pushed the renovate/body-parser-1.x-lockfile branch 2 times, most recently from 35cd0a9 to 50395cc Compare February 4, 2024 14:30
@renovate renovate bot force-pushed the renovate/body-parser-1.x-lockfile branch from 50395cc to 1a02d33 Compare February 26, 2024 02:10
@renovate renovate bot force-pushed the renovate/body-parser-1.x-lockfile branch from 1a02d33 to 3702fee Compare March 13, 2024 08:41
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.

None yet

0 participants