Skip to content

fix(deps): bump follow-redirects from 1.16.0 to 1.16.1 - #476

Open
dependabot[bot] wants to merge 3 commits into
mainfrom
dependabot/npm_and_yarn/follow-redirects-1.16.1
Open

dependabot[bot] wants to merge 3 commits into
mainfrom
dependabot/npm_and_yarn/follow-redirects-1.16.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 21, 2026

Copy link
Copy Markdown
Contributor

Bumps follow-redirects from 1.16.0 to 1.16.1.

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will 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.

Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.16.0 to 1.16.1.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](follow-redirects/follow-redirects@v1.16.0...v1.16.1)

---
updated-dependencies:
- dependency-name: follow-redirects
  dependency-version: 1.16.1
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@vercel

vercel Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
cli-web-cli Ready Ready Preview Oct 21, 2026 1:53pm UTC

Request Review

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Oct 21, 2026
The pnpm security override for follow-redirects was pinning vulnerable
versions (<=1.15.11) to 1.16.0. Now that 1.16.1 is available, update
the override target to 1.16.1 and regenerate the lockfile so the
indirect dependency (via http-server → http-proxy) also resolves to
the latest patch version.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@ci-lockfile-regen

Copy link
Copy Markdown

Dependabot Fix Assessment

Package: `follow-redirects` `1.16.0` → `1.16.1` (patch)
Scope: devDependency (indirect — via `http-server@14.1.1` → `http-proxy@1.18.1`)
Workspace: root

What changed upstream

  • 1.16.1: Support key/value header arrays; escape all RegExp modifiers
  • Pure bug fixes — no breaking changes

Migration concerns checked

  • Peer dependencies: OK (no peer dep changes)
  • Type changes: OK (no type changes in 1.16.1)
  • Config files: OK
  • Module format: OK (CommonJS, unchanged)
  • React compatibility: N/A
  • Monorepo impact: Only used in root workspace (via devDependency http-server)

What broke

  • Web CLI E2E Tests (Parallel): Dependabot's original lockfile commit did not include the overrides section that our current pnpm.overrides config in package.json requires. pnpm reported ERR_PNPM_LOCKFILE_CONFIG_MISMATCH during pnpm install --frozen-lockfile.
  • E2E Tests: Same root cause — lockfile mismatch failed the install step.

Root cause

Dependabot regenerated the lockfile with an older pnpm version that didn't record the pnpm.overrides section in pnpm-lock.yaml. A subsequent workflow committed a lockfile fix (9bc768f) that resolved the mismatch, but that regeneration left the lockfile at follow-redirects@1.16.0 (identical to main) — the actual bump to 1.16.1 was never completed.

What was fixed

  1. package.json: Updated security override target from 1.16.0 → 1.16.1 (override range <=1.15.11 unchanged — that targets the original CVE-affected versions)
  2. pnpm-lock.yaml: Ran pnpm update follow-redirects to resolve follow-redirects to 1.16.1 across the dependency graph (previously pinned at 1.16.0 by the lockfile)

Verification

  • Build: ✅ (pnpm prepare succeeded)
  • Lint: ✅ (0 errors, 10 pre-existing warnings)
  • Unit tests: ✅ (188 test files passed, 2645 tests)
  • Web CLI tests: N/A (no changes to web-cli code)

Notes for reviewer

  • No application code changes needed — follow-redirects is not imported directly by this repo
  • The pnpm.overrides entry "follow-redirects@<=1.15.11": "1.16.1" ensures any transitive dependency that requests an old vulnerable version gets upgraded to 1.16.1

This branch was successfully deployed

1 active deployment
Preview — 9b86dd4f Deployed Oct 21, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Development

Successfully merging this pull request may close these issues.

0 participants