| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.9 to 1.16.0. - [Release notes](https://github.com/follow-redirects/follow-redirects/releases) - [Commits](follow-redirects/follow-redirects@v1.15.9...v1.16.0) --- updated-dependencies: - dependency-name: follow-redirects dependency-version: 1.16.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
|
I triggered the creation of this PR from a Dependabot alert as a test. |
Sorry, something went wrong.
There was a problem hiding this comment.
Makes sense as a change; the meta-question here is whether this should be tagged for back ported to 3.15 and 3.14? I presume so; but is there any way to make that happen automatically?
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Bumps follow-redirects from 1.15.9 to 1.16.0.
CommitsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
You can disable automated security fix PRs for this repo from the Security Alerts page.