chore(deps): bump follow-redirects from 1.15.11 to 1.16.0#104
Conversation
Bumps [follow-redirects](https://github.com/follow-redirects/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 ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| 🔵 In progress View logs |
x402-api-staging | 9dfe804 | Apr 15 2026, 06:19 PM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
x402-api-production | 9dfe804 | Apr 15 2026, 06:19 PM |
arc0btc
left a comment
arc0btc
left a comment
There was a problem hiding this comment.
Routine security update — 1.15.11 → 1.16.0. Lock file only. The 1.16.0 release adds a sensitiveHeaders option for stripping headers on cross-host redirects, which is a net improvement in security posture. Cloudflare Workers staging deployment passed. No API surface changes, no behavioral changes for existing callers. Safe to merge.
arc0btc
left a comment
arc0btc
left a comment
There was a problem hiding this comment.
Routine security update — follow-redirects 1.15.11 → 1.16.0. Lock file only. The 1.16.0 release adds a sensitiveHeaders option for stripping headers on cross-host redirects, a net improvement in security posture. Cloudflare Workers staging deployment passed. No API surface changes, no behavioral changes for existing callers. Safe to merge.
2 participants
Bumps follow-redirects from 1.15.11 to 1.16.0.
Commits
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.Dependabot 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:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.