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

refactor: upgrade body-parser from 1.19.1 to 1.19.2 #2057

Merged
merged 1 commit into from
Mar 10, 2022

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade body-parser from 1.19.1 to 1.19.2.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 22 days ago, on 2022-02-16.
Release notes
Package name: body-parser
  • 1.19.2 - 2022-02-16
    • 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
  • 1.19.1 - 2021-12-10
    • 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
from body-parser GitHub release notes
Commit messages
Package name: body-parser

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@parse-github-assistant
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title [Snyk] Upgrade body-parser from 1.19.1 to 1.19.2 refactor: upgrade body-parser from 1.19.1 to 1.19.2 Mar 10, 2022
@mtrezza mtrezza merged commit a6f7a3b into alpha Mar 10, 2022
@mtrezza mtrezza deleted the snyk-upgrade-afd26b2b091e102f958db9af5a25c5e6 branch March 10, 2022 19:25
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.0.0-alpha.19

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Mar 10, 2022
mtrezza pushed a commit to mtrezza/parse-dashboard that referenced this pull request Mar 23, 2022
dblythy pushed a commit to dblythy/parse-dashboard that referenced this pull request Apr 4, 2022
beiguancyc pushed a commit to beiguancyc/parse-dashboard that referenced this pull request Apr 21, 2022
Merge branch 'release'

* release: (32 commits)
  chore(release): 4.1.0 [skip ci]
  ci: release commit
  chore(release): 4.1.0-beta.1 [skip ci]
  ci: release commit
  chore(release): 4.1.0-alpha.1 [skip ci]
  ci: add backmerge branches (parse-community#2067)
  chore(release): 4.0.0-alpha.21 [skip ci]
  fix: upgrade otpauth from 7.0.10 to 7.0.11 (parse-community#2061)
  chore(release): 4.0.0-alpha.20 [skip ci]
  feat: change string filter description (parse-community#2059)
  chore(release): 4.0.0-alpha.19 [skip ci]
  fix: upgrade express from 4.17.2 to 4.17.3 (parse-community#2058)
  refactor: upgrade body-parser from 1.19.1 to 1.19.2 (parse-community#2057)
  chore(release): 4.0.0-alpha.18 [skip ci]
  fix: upgrade @babel/runtime from 7.17.0 to 7.17.2 (parse-community#2055)
  chore(release): 4.0.0-alpha.17 [skip ci]
  chore(release): 4.0.0-alpha.16 [skip ci]
  ci: bump environment
  chore(release): 4.0.0-beta.4 [skip ci]
  ci: release commit
  ...

# Conflicts:
#	package-lock.json
dblythy pushed a commit to dblythy/parse-dashboard that referenced this pull request Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released-alpha Released as alpha version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants