[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
supertest	7.3.0 → 7.3.1

---

Release Notes

ladjs/supertest (supertest)

v7.3.1

Compare Source

• Merge pull request #​907 from JH8459/fix/ephemeral-loopback-bind 884cd26
• fix: bind ephemeral server to the loopback address it connects to e74a1e0

---

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Dependency Upgrade Analysis

PR: #167 chore(deps): update dependency supertest to v7.3.1
Analyzed on: 2026-10-18 01:16 UTC
Triggered by: push to renovate/supertest-7.x-lockfile

Overall risk assessment

Package / Action	From	To	Risk	Action
supertest	7.3.0	7.3.1	Low	Proceed

---

supertest — 7.3.0 → 7.3.1

Section: devDependencies
Changelog: https://github.com/forwardemail/supertest/releases/tag/v7.3.1

Summary

This is a patch release (7.3.0 → 7.3.1) that fixes how the ephemeral HTTP server binds to the loopback address. There are no documented breaking changes, no new deprecations, and the change is localized to server binding behavior in test contexts. Project impact is expected to be minimal given supertest appears only as a devDependency with no direct imports found in the source code.

Breaking changes

No breaking changes documented between 7.3.0 and 7.3.1.

Deprecations

No new deprecations documented between 7.3.0 and 7.3.1.

Performance

No performance changes documented between 7.3.0 and 7.3.1. Consider benchmarking before shipping if your test suite performance is critical.

New APIs

No new public APIs documented between 7.3.0 and 7.3.1.

Configuration & environment

• Node.js version compatibility: supertest requires node >= 14.18.0. The project’s .nvmrc specifies v24.9.0 (based on project docs), which satisfies this constraint.
• Peer-dependency constraints: None documented; supertest depends on superagent, methods, and cookie-signature.
• TypeScript constraints: No documented TypeScript compatibility changes.
• Default config changes: None documented.
• Lockfile regeneration notes: The upgrade updates supertest and its transitive resolution; pnpm-lock.yaml should be regenerated/updated (it already reflects 7.3.1 in the working tree).

Project usage audit

• Files importing the package: 0 matches found in src/. Grepping for supertest across source code returned no results.
• APIs used: None detected in application code (supertest is typically used in E2E/integration tests). Project test setup uses Jest (jest.config.ts with ts-jest); no E2E test files were found in the repository at this time.
• APIs NOT used: All supertest APIs remain unused by the application codebase.

Migration plan

1. Install/refresh dependencies: Run pnpm install to ensure lockfile consistency with the updated version.
2. Run tests: Execute pnpm test (unit tests) and any E2E tests (pnpm test:e2e if configured) to verify behavior is unaffected.
3. Lint/typecheck: Run pnpm lint and TypeScript checks (tsc --noEmit if applicable) as per project conventions.
4. Manual verification: The change only affects ephemeral server binding (loopback) in test contexts; this should not affect production behavior. No code changes are expected.

---

References

• supertest v7.3.1 Release Notes
• supertest npm package

[github-actions]

Auto-analysis: all dependency upgrades assessed as Low risk / Proceed. Auto-merge enabled; GitHub will merge once CI checks pass.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!