Skip to content

fix(examples): apply Express and NestJS security updates - #928

Open
bnusunny wants to merge 1 commit into
mainfrom
fix/express-nest-sweep
Open

bnusunny wants to merge 1 commit into
mainfrom
fix/express-nest-sweep

Conversation

@bnusunny

@bnusunny bnusunny commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Applies the security updates from 4 stale or conflicting Dependabot PRs by hand.

Testing

After the rebase: sls/nestjs pnpm install --frozen-lockfile and nest build pass; pnpm why shows path-to-regexp 0.1.13 (no 0.1.7) and follow-redirects 1.16.3. npm ci passes in sqs-expressjs and both datadog Express examples. check-example-config.sh passes. Audit counts were not re-run after the rebase.

Replaces #748, #738, #731, #726.

@bnusunny
bnusunny requested a review from a team as a code owner November 13, 2026 19:51
Hand-applied security updates for sqs-expressjs and sls/nestjs,
replacing 4 stale or conflicting Dependabot PRs.

- sqs-expressjs: qs 6.15.x -> 6.16.2 (npm update qs). The two datadog
  Express examples already have qs 6.16.2 on main (#924, #925).
- sls/nestjs: pnpm override path-to-regexp@<0.1.13 -> 0.1.13. express
  4.18.2 pins path-to-regexp 0.1.7 exactly, so no update can lift it;
  the override is what `pnpm audit --fix` would write for this one
  advisory. Rebased onto #934 (follow-redirects 1.16.3). The only
  resolved-version change in pnpm-lock.yaml is path-to-regexp
  0.1.7 -> 0.1.13; the rest is pnpm 9.15 re-serializing peer suffixes.
@bnusunny
bnusunny force-pushed the fix/express-nest-sweep branch from 1ba2f66 to 8cde719 Compare November 16, 2026 18:02
@bnusunny
bnusunny requested a review from vicheey November 20, 2026 15:30

This branch has not been deployed

No deployments
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.

1 participant