Skip to content

chore(deps): bump the npm-minor-patch group across 1 directory with 3 updates - #1562

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-minor-patch-95e1384485
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-minor-patch-95e1384485

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the npm-minor-patch group with 3 updates in the / directory: express-rate-limit, supertest and viem.

Updates express-rate-limit from 8.7.3 to 8.7.4

Release notes

Sourced from express-rate-limit's releases.

v8.7.4

You can view the changelog here.

Commits

Updates supertest from 7.3.1 to 7.3.2

Release notes

Sourced from supertest's releases.

v7.3.2

  • fix: keep the shared server alive for every request that uses it 2a5e96f

forwardemail/supertest@v7.3.1...v7.3.2

Commits

Updates viem from 2.57.16 to 2.57.19

Release notes

Sourced from viem's releases.

viem@2.57.19

Patch Changes

viem@2.57.18

Patch Changes

... (truncated)

Commits
  • 9442320 chore: version package (#5489)
  • f3fe670 fix(actions): resolve nested actions through getAction (#5495)
  • 08a463a fix(tempo): return the zero commitment from getConfigCommitment on chains w...
  • e87e3ec fix(tempo): reject a retired root key in the verifyHash hook (#5498)
  • a0ddd34 fix(tempo): answer the relay's 413 without awaiting the body cancel (#5496)
  • 1e117b1 feat(chains): add Kinetiq Elysium (99901) and Elysium Testnet (99801) (#5490)
  • cd91b17 fix: append ErrorType to three action error unions (#5493)
  • be88182 docs(tokens): add chainId to importing-tokens example, sort OUSD addresses ...
  • 0fee300 Two error classes never pass name to super, and one ErrorType alias poi...
  • 5c6a920 feat(tokens): add chainId to ResolvedToken, add OUSD on Tempo Moderato (#...
  • Additional commits viewable in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

… updates

Bumps the npm-minor-patch group with 3 updates in the / directory: [express-rate-limit](https://github.com/express-rate-limit/express-rate-limit), [supertest](https://github.com/ladjs/supertest) and [viem](https://github.com/wevm/viem).


Updates `express-rate-limit` from 8.7.3 to 8.7.4
- [Release notes](https://github.com/express-rate-limit/express-rate-limit/releases)
- [Commits](express-rate-limit/express-rate-limit@v8.7.3...v8.7.4)

Updates `supertest` from 7.3.1 to 7.3.2
- [Release notes](https://github.com/ladjs/supertest/releases)
- [Commits](forwardemail/supertest@v7.3.1...v7.3.2)

Updates `viem` from 2.57.16 to 2.57.19
- [Release notes](https://github.com/wevm/viem/releases)
- [Commits](https://github.com/wevm/viem/compare/viem@2.57.16...viem@2.57.19)

---
updated-dependencies:
- dependency-name: express-rate-limit
  dependency-version: 8.7.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: supertest
  dependency-version: 7.3.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: viem
  dependency-version: 2.57.19
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 16, 2026
@strix-security

strix-security Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Strix Security Review

✅ No open security findings.

PR summary: Bumps three dependencies within their minor/patch ranges: express-rate-limit 8.7.3 to 8.7.4, supertest 7.3.1 to 7.3.2 and viem 2.57.16 to 2.57.19, updating package.json and the lockfile without touching application code.

Review summary

No security issues found in the changed code. The pull request only raises three dependency versions in package.json and their corresponding package-lock.json entries (express-rate-limit 8.7.3 to 8.7.4, supertest 7.3.1 to 7.3.2, viem 2.57.16 to 2.57.19) together with the transitively resolved superagent, qs, form-data, hasown and ox versions. No application source, configuration, route, middleware or CI file is modified, no new package is introduced, every changed entry still resolves from the public npm registry with a matching integrity hash, and no dependency moves between the runtime and development sets. All three upgrades are patch releases whose upstream content is hardening rather than a behaviour change: the express-rate-limit fix stops the in-memory store from returning already-expired entries and hardens the decrement path that no limiter in this repository configures, while the viem fixes tighten signature verification, ABI decoding size limits and ENS/CCIP-Read response bounds, and viem itself is only reachable from local end-to-end scripts. Nothing in the diff exposes new input handling or weakens an existing control.

Ruled out (3)
  • Does the express-rate-limit patch change rate-limiting behaviour in a way that lets a client exceed its intended quota?
    The 8.7.4 changes stop the in-memory store from returning expired clients and harden the decrement path, neither of which can make counting more permissive, and no limiter in this repository sets a custom store or the skip options that invoke decrement.
  • Could the viem patch alter signature, ABI decoding or chain-address handling used by production verification code?
    viem is a development dependency used only by local end-to-end scripts, and every production verification path runs through ethers 6.17, which this change does not touch.
  • Does the lockfile update pull in a new package, a different registry or a build-time install hook from an unexpected source?
    The diff only re-versions eight packages that were already present, all resolved from the public npm registry with updated integrity hashes, and no new install scripts or registry sources are added.

Review 1 on this PR · 48c743b · requested Nov 16 05:52 UTC when the PR was opened


Reviewed by Strix
Re-run review · Configure security review settings · Try a deeper review with @strix-security /deep

@strix-security strix-security Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No security issues found in the changed code. The pull request only raises three dependency versions in package.json and their corresponding package-lock.json entries (express-rate-limit 8.7.3 to 8.7.4, supertest 7.3.1 to 7.3.2, viem 2.57.16 to 2.57.19) together with the transitively resolved superagent, qs, form-data, hasown and ox versions. No application source, configuration, route, middleware or CI file is modified, no new package is introduced, every changed entry still resolves from the public npm registry with a matching integrity hash, and no dependency moves between the runtime and development sets. All three upgrades are patch releases whose upstream content is hardening rather than a behaviour change: the express-rate-limit fix stops the in-memory store from returning already-expired entries and hardens the decrement path that no limiter in this repository configures, while the viem fixes tighten signature verification, ABI decoding size limits and ENS/CCIP-Read response bounds, and viem itself is only reachable from local end-to-end scripts. Nothing in the diff exposes new input handling or weakens an existing control.


Reviewed by Strix
Configure security review settings

@dependabot @github

dependabot Bot commented on behalf of github Nov 17, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Nov 17, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/npm-minor-patch-95e1384485 branch November 17, 2026 01:17
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 javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants