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 punycode from 1.3.2 to 1.4.1 #24

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade punycode from 1.3.2 to 1.4.1.

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 2 versions ahead of your current version.
  • The recommended version was released 6 years ago, on 2016-03-20.
Release notes
Package name: punycode from punycode GitHub release notes
Commit messages
Package name: punycode
  • 0fbadd6 Release v1.4.1
  • 952c3ea Release v1.4.0
  • 60cdef6 Add jspm Node support
  • 56fb69c Update dependencies
  • 702cc2d Add `new` to RangeError
  • cddec52 Test in Node.js v0.12, io.js, and Rhino 1.7R5
  • e1d4f59 Document the fact that `toASCII` expects normalized input
  • 30f8154 Update IETF URLs to use HTTPS

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

snyk-bot and others added 7 commits February 23, 2022 05:27
…c0e6aac9aa

[Snyk] Security upgrade node from 14-slim to current-slim
…6bc8352ddb

[Snyk] Fix for 3 vulnerabilities
…911a7f4f16

[Snyk] Security upgrade node from 14-slim to gallium-buster-slim
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.

2 participants