GeezerVison

The lockfile edit is valid today, but nothing keeps follow-redirects at 1.16.2 afterward.

follow-redirects is only a transitive dependency of [email protected], which declares ^1.16.0. Because 1.16.2 satisfies that range, pnpm install --frozen-lockfile passes. A later pnpm update, lockfile regeneration, or axios bump re-resolves it, and the lockfile edit gives no guarantee it stays at 1.16.2.

This repo already pins transitive dependencies under overrides: in site/pnpm-workspace.yaml (semver, esbuild, qs, dompurify, and others). Please add follow-redirects there and regenerate the lockfile with pnpm install, so the lockfile also records the override:

overrides:
  follow-redirects: 1.16.2

I suggest an exact pin to match saveExact: true and the other overrides. Use ^1.16.2 if you want patch updates to flow through.

If this bump is a routine refresh and not a security floor, the current diff is acceptable. Please say which in the PR description.

I did not compare the new integrity hash against the registry.