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 file-saver from 2.0.1 to 2.0.2 #41

Merged
merged 1 commit into from Mar 27, 2020

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade file-saver from 2.0.1 to 2.0.2.

ℹ️ 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 10 months ago, on 2019-05-14.
Release notes
Package name: file-saver
  • 2.0.2 - 2019-05-14
    • Catching an exception on Send (HEAD) (#534)
  • 2.0.1 - 2019-02-17
from file-saver GitHub release notes
Commit messages
Package name: file-saver
  • 1bc9ed3 bump minor version
  • 71f266f Missing dist build
  • 9bd5261 Catching an exception on Send. This happens when request for HEAD returns 405 Method Not Allowed. Instead of error http status, this may throw an exception. Return false and fallback to link download.
  • 3caf053 fix autoBom documentation
  • 04ca364 Updated Chrome data
  • d87b419 Update README.md

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

@jupe jupe merged commit d782af3 into master Mar 27, 2020
@jupe jupe deleted the snyk-upgrade-14dec19b28bb4b76f1111f6a7d4a3f81 branch March 27, 2020 21:16
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

2 participants