Bump follow-redirects from 1.15.11 to 1.16.0 in /functions/remediators/remediateGoogleAPIKey in the npm_and_yarn group across 1 directory#62
Conversation
353a68f to
95e5ae2
Compare
|
@dependabot recreate |
Bumps the npm_and_yarn group with 1 update in the /functions/remediators/remediateGoogleAPIKey directory: [follow-redirects](https://github.com/follow-redirects/follow-redirects). Updates `follow-redirects` from 1.15.11 to 1.16.0 - [Release notes](https://github.com/follow-redirects/follow-redirects/releases) - [Commits](follow-redirects/follow-redirects@v1.15.11...v1.16.0) --- updated-dependencies: - dependency-name: follow-redirects dependency-version: 1.16.0 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
95e5ae2 to
9c1f776
Compare
…oogle remediation
Fixed in f548c28. Two issues were causing the CI failures:
|
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Fixed in the latest commit. Two issues were causing the CI failures:
|
Bumps the npm_and_yarn group with 1 update in the /functions/remediators/remediateGoogleAPIKey directory: follow-redirects.
Updates
follow-redirectsfrom 1.15.11 to 1.16.0Commits
0c23a22Release version 1.16.0 of the npm package.844c4d3Add sensitiveHeaders option.5e8b8d0ci: add Node.js 24.x to the CI matrix7953e22ci: upgrade GitHub Actions to use setup-node@v6 and checkout@v686dc1f8Sanitizing input.