Skip to content

Update follow-redirects to 1.16.2 - #1002

Merged
KrzysztofPajak merged 1 commit into
developfrom
fix/follow-redirects-1.16.2
Oct 31, 2026
Merged

KrzysztofPajak merged 1 commit into
developfrom
fix/follow-redirects-1.16.2

Conversation

@KrzysztofPajak

Copy link
Copy Markdown
Member

Type: bugfix

Issue

The Scan repository job of the Trivy workflow fails on develop (run 41178316895). The Trivy filesystem gate step reports follow-redirects 1.16.1 in src/Web/Grand.Web/vueapp/package-lock.json as CVE-2026-116689 (HIGH), fixed in 1.16.2.

The package comes in through axios. No commit introduced the failure: the finding arrived with the vulnerability database.

Solution

Move follow-redirects to 1.16.2 in the lockfile. The axios range (^1.16.0) already allows it, so package.json does not change.

Only the three lines of that package's entry change. npm update on npm 10.9 also strips the libc fields of the native optional packages, so that part was left out.

The committed bundles do not change: they contain no follow-redirects code, and a build on 1.16.1 and a build on 1.16.2 produce the same SHA-256 for all four bundle files.

Breaking changes

None.

Testing

  1. In src/Web/Grand.Web/vueapp, run npm ci. It installs follow-redirects 1.16.2.
  2. Run npm run audit:prod. It reports 0 vulnerabilities.
  3. Run npm run build, then git diff --stat --ignore-space-at-eol. No bundle has a content change.
  4. Check that the Scan repository job of the Trivy workflow passes on this pull request.

The Trivy filesystem gate fails on develop: 1.16.1 has CVE-2026-116689, fixed in 1.16.2. The package comes in through axios, whose range already allows the new version, so only the lockfile moves.
Copilot AI balanced review requested due to automatic review settings October 31, 2026 07:49

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

@KrzysztofPajak
KrzysztofPajak merged commit 95ed824 into develop Oct 31, 2026
9 checks passed
@KrzysztofPajak
KrzysztofPajak deleted the fix/follow-redirects-1.16.2 branch October 31, 2026 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants