Skip to content

refactor: upgrade follow-redirects from 1.14.2 to 1.14.4 #7694

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
Nov 12, 2021

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade follow-redirects from 1.14.2 to 1.14.4.

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 2 months ago, on 2021-09-14.
Release notes
Package name: follow-redirects from follow-redirects GitHub release notes
Commit messages
Package name: follow-redirects
  • 77e2a58 Release version 1.14.4 of the npm package.
  • eb6e76f Fix another self mention.
  • f26c6c6 Release version 1.14.3 of the npm package.
  • 3f1b2f5 Fix timeout clearing.

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

@parse-github-assistant
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.14.2 to 1.14.4 refactor: upgrade follow-redirects from 1.14.2 to 1.14.4 Nov 12, 2021
@codecov
Copy link

codecov bot commented Nov 12, 2021

Codecov Report

Merging #7694 (63627d7) into alpha (611bd9b) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

❗ Current head 63627d7 differs from pull request most recent head 6177628. Consider uploading reports for the commit 6177628 to get more accurate results
Impacted file tree graph

@@            Coverage Diff             @@
##            alpha    #7694      +/-   ##
==========================================
- Coverage   93.90%   93.89%   -0.02%     
==========================================
  Files         183      183              
  Lines       13626    13624       -2     
==========================================
- Hits        12796    12792       -4     
- Misses        830      832       +2     
Impacted Files Coverage Δ
src/ParseServer.js 90.05% <100.00%> (-0.11%) ⬇️
src/batch.js 91.37% <0.00%> (-1.73%) ⬇️
src/Adapters/Files/GridFSBucketAdapter.js 79.50% <0.00%> (-0.82%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d72717d...6177628. Read the comment docs.

@mtrezza mtrezza merged commit e4aa1cb into alpha Nov 12, 2021
@mtrezza mtrezza deleted the snyk-upgrade-9733db2c01fc4d14a1446c280a66adca branch November 12, 2021 23:47
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 5.0.0-alpha.8

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Nov 18, 2021
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 5.0.0-beta.10

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Mar 15, 2022
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 5.1.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released Released as stable version state:released-alpha Released as alpha version state:released-beta Released as beta version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants