Skip to content

[Snyk] Upgrade @parse/node-apn from 4.1.0 to 4.1.1 #188

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

Merged
merged 1 commit into from
May 10, 2021

Conversation

snyk-bot
Copy link
Contributor

@snyk-bot snyk-bot commented May 8, 2021

Snyk has created this PR to upgrade @parse/node-apn from 4.1.0 to 4.1.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 1 version ahead of your current version.
  • The recommended version was released 21 days ago, on 2021-04-16.
Release notes
Package name: @parse/node-apn
  • 4.1.1 - 2021-04-16
    • FIX: add proxy and fix logger types
    • NEW: Added support for critical notifications
  • 4.1.0 - 2021-04-14
    • NEW: Proxy support
    • FIX: Close client on unexpected frame error
    • NEW: Add a configurable info/error logger
    • FIX: Update endpoint address
    • FIX: Add support to zero valued expiry
from @parse/node-apn GitHub release notes
Commit messages
Package name: @parse/node-apn

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

@davimacedo davimacedo merged commit 2a6fca7 into master May 10, 2021
@mtrezza mtrezza deleted the snyk-upgrade-96f12781b3300f845d1166d70a6b1efc branch November 21, 2021 16:02
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