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 got from 8.2.0 to 8.3.2 #41

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade got from 8.2.0 to 8.3.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 3 versions ahead of your current version.
  • The recommended version was released 4 years ago, on 2018-07-03.
Release notes
Package name: got
  • 8.3.2 - 2018-07-03

    Fix Got throwing an error in some cases when trying to pipe one got.stream into another one. 7ac705f

  • 8.3.1 - 2018-05-01
    • No longer overrides accept-encoding header if already provided. 81f2537
    • Sets content-length header when using form-data if not already set. de9514d
    • Now clears the progress interval if the socket has been destroyed. 82763c8

    v8.3.0...v8.3.1

  • 8.3.0 - 2018-03-09
    • Fixed socket connect memory leak. 13d6b68
    • Prevented uncaught exception in some cases. 43b51ba
    • No longer continues the request after cancelation. 9a646a3

    v8.2.0...v8.3.0

  • 8.2.0 - 2018-02-19

    No longer sets the default accept-encoding: gzip,deflate header if the decompress option is false.

    v8.1.0...v8.2.0

from got GitHub release notes
Commit messages
Package name: got

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

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.

1 participant