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

[Snyk] Upgrade qs from 6.12.0 to 6.12.1 #116

Closed

Conversation

arddluma
Copy link
Member

@arddluma arddluma commented May 4, 2024

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade qs from 6.12.0 to 6.12.1.

ℹ️ 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 21 days ago, on 2024-04-12.
Release notes
Package name: qs from qs GitHub release notes
Commit messages
Package name: qs
  • 59d765f v6.12.1
  • 7e18298 [Fix] `parse`: Disable `decodeDotInKeys` by default to restore previous behavior
  • fd3cd7a [Tests] increase coverage
  • 6d7df02 [Performance] `utils`: Optimize performance under large data volumes, reduce memory usage, and speed up processing
  • 572533c [Refactor] `utils`: use `+=`
  • c4d29f3 [meta] add tea.yaml

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

Copy link

github-actions bot commented May 4, 2024

Yooo! You forgot to bump the version in package.json!

@arddluma arddluma closed this May 22, 2024
@arddluma arddluma deleted the snyk-upgrade-18698f1bd672150ca72db45e0c5a30f3 branch May 22, 2024 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants