Skip to content

chore(deps): update dependency viem to v2.48.4#1517

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/viem-2.x
Open

chore(deps): update dependency viem to v2.48.4#1517
renovate[bot] wants to merge 1 commit intomainfrom
renovate/viem-2.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jan 9, 2026

This PR contains the following updates:

Package Type Update Change OpenSSF
viem (source) devDependencies minor 2.43.52.48.4 OpenSSF Scorecard

Release Notes

wevm/viem (viem)

v2.48.4

Compare Source

Patch Changes
  • #​4532 cb3206e1039b21e45e4ed17898aa1ff561cdecb4 Thanks @​jxom! - viem/tempo: Added virtual address actions for the TIP-1022 Address Registry precompile: virtualAddress.getMasterAddress, virtualAddress.resolve, virtualAddress.registerMaster, virtualAddress.registerMasterSync. Re-exported VirtualAddress and VirtualMaster from ox/tempo.

v2.48.3

Compare Source

v2.48.2

Compare Source

Patch Changes

v2.48.1

Compare Source

Patch Changes

v2.48.0

Compare Source

Minor Changes

v2.47.19

Compare Source

Patch Changes

v2.47.18

Compare Source

Patch Changes

v2.47.17

Compare Source

Patch Changes

v2.47.16

Compare Source

Patch Changes

v2.47.15

Compare Source

Patch Changes

v2.47.14

Compare Source

Patch Changes

v2.47.12

Compare Source

Patch Changes

v2.47.11

Compare Source

Patch Changes

v2.47.10

Compare Source

Patch Changes

v2.47.6

Compare Source

Patch Changes

v2.47.5

Compare Source

Patch Changes

v2.47.4

Compare Source

Patch Changes

v2.47.2

Compare Source

Patch Changes

v2.47.1

Compare Source

Patch Changes

v2.47.0

Compare Source

Minor Changes
  • 1adb83804d5f6c3f36d5f293de88532330d52dc7 Thanks @​jxom! - Breaking (viem/tempo): chainId is now required when signing access key authorizations with signKeyAuthorization. It is recommended to use client.accessKey.signAuthorization instead for inferred chain ID.

    import { client } from './viem.config'
    import { Account } from 'viem/tempo'
    
    const account = Account.from({ privateKey: '0x...' })
    const accessKey = Account.fromP256(generatePrivateKey(), {
      access: account,
    })
    
    - const keyAuthorization = await account.signKeyAuthorization(accessKey)
    + const keyAuthorization = await client.accessKey.signAuthorization({
    +   account,
    +   accessKey,
    + })
Patch Changes

v2.46.3

Compare Source

Patch Changes

v2.46.2

Compare Source

Patch Changes

v2.46.1

Compare Source

Patch Changes

v2.46.0

Compare Source

Minor Changes
  • #​4304 b6b50d40fb6bbadc851377b74b2dd4da584958b0 Thanks @​jxom! - Breaking (viem/tempo): Renamed nonceKey: 'random' to nonceKey: 'expiring' to align with TIP-1009 terminology.

    TIP-1009 defines "expiring nonces" as time-based replay protection using validBefore timestamps. The name 'expiring' better describes the mechanism than 'random'.

    await sendTransaction(client, {
      account,
    - nonceKey: 'random',
    + nonceKey: 'expiring',
      to: '0x...',
    })

v2.45.3

Compare Source

Patch Changes

v2.45.2

Compare Source

Patch Changes

v2.45.1

Compare Source

Patch Changes

v2.45.0

Compare Source

Minor Changes
Patch Changes

v2.44.4

Compare Source

Patch Changes

v2.44.2

Compare Source

Patch Changes

v2.44.1

Compare Source

Patch Changes

v2.44.0

Compare Source

Minor Changes
  • #​4201 0268ca88c67c7851ae03d8d41508657f2b62729d Thanks @​jxom! - ### viem/tempo Extension

    Added support for Tempo Moderato testnet.

    • (Breaking): Renamed tempoTestnettempoModerato. The old export is deprecated but still available as an alias.
    • (Breaking): Renamed reward.startreward.distribute: Renamed for distributing rewards (no longer supports streaming).
    • (Breaking): Renamed reward.getTotalPerSecondreward.getGlobalRewardPerToken: Returns the global reward per token value instead of per-second rate.
    • (Breaking): Renamed reward.watchRewardScheduledreward.watchRewardDistributed: Watches for reward distributed events.
    • (Breaking): Removed nonce.getNonceKeyCount.
    • (Breaking): Removed nonce.watchActiveKeyCountChanged.
    • (Breaking): Removed amm.watchFeeSwap (FeeSwap event no longer emitted by protocol).
    • (Breaking): OrderPlaced event now includes isFlipOrder and flipTick fields. The FlipOrderPlaced event has been removed and merged into OrderPlaced.
    • (Breaking): Renamed Address.stablecoinExchangeAddress.stablecoinDex.
    • (Breaking): Renamed Abis.stablecoinExchangeAbis.stablecoinDex.
    • Added dex.cancelStale action to cancel stale orders from restricted makers.
    • Added salt parameter to token.create.
Patch Changes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
    • Only on Sunday and Saturday (* * * * 0,6)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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.

@renovate renovate Bot added the dependencies Dependency updates label Jan 9, 2026
@renovate renovate Bot enabled auto-merge (squash) January 9, 2026 02:42
@github-actions github-actions Bot added qa:running QA workflow is currently running status:approved Pull request has been approved labels Jan 9, 2026
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

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

No issues found across 2 files

@renovate renovate Bot force-pushed the renovate/viem-2.x branch from a4dcdf6 to d0321a3 Compare January 10, 2026 02:22
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.44.0 chore(deps): update dependency viem to v2.44.1 Jan 10, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from d0321a3 to 188bd34 Compare January 13, 2026 12:49
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.44.1 chore(deps): update dependency viem to v2.44.2 Jan 13, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 188bd34 to 8c25b03 Compare January 15, 2026 23:03
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.44.2 chore(deps): update dependency viem to v2.44.4 Jan 15, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 8c25b03 to 706fb3b Compare January 25, 2026 10:45
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.44.4 chore(deps): update dependency viem to v2.45.0 Jan 25, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 706fb3b to e1d0c65 Compare January 30, 2026 02:34
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.45.0 chore(deps): update dependency viem to v2.45.1 Jan 30, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from e1d0c65 to 577dd32 Compare February 9, 2026 02:49
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.45.1 chore(deps): update dependency viem to v2.45.2 Feb 9, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 577dd32 to 7e31b76 Compare February 11, 2026 06:46
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.45.2 chore(deps): update dependency viem to v2.45.3 Feb 11, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 7e31b76 to a33b008 Compare February 15, 2026 06:14
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.45.3 chore(deps): update dependency viem to v2.46.0 Feb 15, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from a33b008 to d1af8af Compare February 16, 2026 03:07
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.46.0 chore(deps): update dependency viem to v2.46.1 Feb 16, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from d1af8af to 57dd2ae Compare February 18, 2026 00:38
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.46.1 chore(deps): update dependency viem to v2.46.2 Feb 18, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 57dd2ae to 9c6013d Compare February 24, 2026 03:40
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.46.2 chore(deps): update dependency viem to v2.46.3 Feb 24, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 9c6013d to 545c395 Compare March 4, 2026 23:17
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 6ffc4aa to 718a276 Compare March 21, 2026 10:38
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.47.5 chore(deps): update dependency viem to v2.47.6 Mar 21, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 718a276 to d133b4e Compare April 4, 2026 06:17
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.47.6 chore(deps): update dependency viem to v2.47.10 Apr 4, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from d133b4e to 6822ef6 Compare April 9, 2026 07:47
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.47.10 chore(deps): update dependency viem to v2.47.11 Apr 9, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 6822ef6 to c1d8cf0 Compare April 10, 2026 02:46
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.47.11 chore(deps): update dependency viem to v2.47.12 Apr 10, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from c1d8cf0 to 73050d6 Compare April 13, 2026 02:56
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.47.12 chore(deps): update dependency viem to v2.47.14 Apr 13, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 73050d6 to 349e333 Compare April 13, 2026 07:06
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.47.14 chore(deps): update dependency viem to v2.47.15 Apr 13, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 349e333 to 58a9143 Compare April 13, 2026 11:19
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.47.15 chore(deps): update dependency viem to v2.47.16 Apr 13, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 58a9143 to 08f3744 Compare April 14, 2026 02:48
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.47.16 chore(deps): update dependency viem to v2.47.17 Apr 14, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 08f3744 to 31e3d53 Compare April 15, 2026 16:54
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.47.17 chore(deps): update dependency viem to v2.47.18 Apr 15, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 31e3d53 to f4005ba Compare April 16, 2026 13:57
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.47.18 chore(deps): update dependency viem to v2.48.0 Apr 16, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from f4005ba to 5276d05 Compare April 17, 2026 04:05
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.48.0 chore(deps): update dependency viem to v2.48.1 Apr 17, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 5276d05 to a544337 Compare April 21, 2026 03:07
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.48.1 chore(deps): update dependency viem to v2.48.2 Apr 21, 2026
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from a544337 to 1041a7f Compare April 22, 2026 00:30
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.48.2 chore(deps): update dependency viem to v2.48.3 Apr 22, 2026
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 1041a7f to 9af5998 Compare April 22, 2026 04:08
@renovate renovate Bot changed the title chore(deps): update dependency viem to v2.48.3 chore(deps): update dependency viem to v2.48.4 Apr 22, 2026
@socket-security
Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
License policy violation: npm @img/sharp-libvips-darwin-x64 under LGPL-3.0-or-later

License: LGPL-3.0-or-later - The applicable license policy does not permit this license (5) (npm metadata)

License: LGPL-3.0-or-later - The applicable license policy does not permit this license (5) (package/package.json)

From: ?npm/@img/sharp-libvips-darwin-x64@1.2.4

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@img/sharp-libvips-darwin-x64@1.2.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
License policy violation: npm @img/sharp-libvips-linux-arm under LGPL-3.0-or-later

License: LGPL-3.0-or-later - The applicable license policy does not permit this license (5) (npm metadata)

License: LGPL-3.0-or-later - The applicable license policy does not permit this license (5) (package/package.json)

From: ?npm/@img/sharp-libvips-linux-arm@1.2.4

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@img/sharp-libvips-linux-arm@1.2.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
License policy violation: npm @img/sharp-libvips-linux-arm64 under LGPL-3.0-or-later

License: LGPL-3.0-or-later - The applicable license policy does not permit this license (5) (npm metadata)

License: LGPL-3.0-or-later - The applicable license policy does not permit this license (5) (package/package.json)

From: ?npm/@img/sharp-libvips-linux-arm64@1.2.4

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@img/sharp-libvips-linux-arm64@1.2.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
License policy violation: npm @img/sharp-libvips-linux-ppc64 under LGPL-3.0-or-later

License: LGPL-3.0-or-later - The applicable license policy does not permit this license (5) (npm metadata)

License: LGPL-3.0-or-later - The applicable license policy does not permit this license (5) (package/package.json)

From: ?npm/@img/sharp-libvips-linux-ppc64@1.2.4

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@img/sharp-libvips-linux-ppc64@1.2.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
License policy violation: npm @img/sharp-libvips-linux-riscv64 under LGPL-3.0-or-later

License: LGPL-3.0-or-later - The applicable license policy does not permit this license (5) (npm metadata)

License: LGPL-3.0-or-later - The applicable license policy does not permit this license (5) (package/package.json)

From: ?npm/@img/sharp-libvips-linux-riscv64@1.2.4

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@img/sharp-libvips-linux-riscv64@1.2.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
License policy violation: npm @img/sharp-libvips-linux-s390x under LGPL-3.0-or-later

License: LGPL-3.0-or-later - The applicable license policy does not permit this license (5) (npm metadata)

License: LGPL-3.0-or-later - The applicable license policy does not permit this license (5) (package/package.json)

From: ?npm/@img/sharp-libvips-linux-s390x@1.2.4

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@img/sharp-libvips-linux-s390x@1.2.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Dependency updates qa:running QA workflow is currently running status:approved Pull request has been approved

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants