Skip to content

refactor: Upgrade follow-redirects from 1.15.2 to 1.15.5 #8931

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 3 commits into from
Feb 24, 2024

Conversation

parseplatformorg
Copy link
Contributor

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


Snyk has created this PR to upgrade follow-redirects from 1.15.2 to 1.15.5.

ℹ️ 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 a month ago, on 2024-01-12.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Improper Input Validation
SNYK-JS-FOLLOWREDIRECTS-6141137
686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: follow-redirects from follow-redirects GitHub release notes
Commit messages
Package name: follow-redirects
  • b1677ce Release version 1.15.5 of the npm package.
  • d8914f7 Preserve fragment in responseUrl.
  • 6585820 Release version 1.15.4 of the npm package.
  • 7a6567e Disallow bracketed hostnames.
  • 05629af Prefer native URL instead of deprecated url.parse.
  • 1cba8e8 Prefer native URL instead of legacy url.resolve.
  • 72bc2a4 Simplify _processResponse error handling.
  • 3d42aec Add bracket tests.
  • bcbb096 Do not directly set Error properties.
  • 192dbe7 Release version 1.15.3 of the npm package.
  • bd8c81e Fix resource leak on destroy.
  • 9c728c3 Split linting and testing.
  • d388fe2 build: harden ci.yml permissions

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

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title [Snyk] Upgrade follow-redirects from 1.15.2 to 1.15.5 refactor: Upgrade follow-redirects from 1.15.2 to 1.15.5 Feb 20, 2024
Copy link

Thanks for opening this pull request!

  • ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

Copy link

codecov bot commented Feb 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.34%. Comparing base (70e0cb3) to head (ebf8b0a).

Additional details and impacted files
@@                Coverage Diff                @@
##           release-6.x.x    #8931      +/-   ##
=================================================
+ Coverage          94.32%   94.34%   +0.02%     
=================================================
  Files                186      186              
  Lines              14827    14827              
=================================================
+ Hits               13985    13989       +4     
+ Misses               842      838       -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mtrezza mtrezza merged commit 4524c35 into release-6.x.x Feb 24, 2024
@mtrezza mtrezza deleted the snyk-upgrade-2451a0349cdca5ed1500927a8b990355 branch February 24, 2024 16:30
@parseplatformorg
Copy link
Contributor Author

🎉 This change has been released in version 6.5.0

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.

3 participants