Skip to content

fix(deps): update dependency viem to v2 - #8

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

fix(deps): update dependency viem to v2#8
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/viem-2.x

Conversation

@renovate

@renovate renovate Bot commented Jan 22, 2024

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
viem (source) ^1.19.11^2.0.0 age confidence

Release Notes

wevm/viem (viem)

v2.55.19

Compare Source

Patch Changes

v2.55.18

Compare Source

Patch Changes

v2.55.17

Compare Source

Patch Changes

v2.55.16

Compare Source

Patch Changes

v2.55.15

Compare Source

Patch Changes

v2.55.13

Compare Source

Patch Changes

v2.55.11

Compare Source

Patch Changes

v2.55.10

Compare Source

Patch Changes

v2.55.8

Compare Source

Patch Changes

v2.55.7

Compare Source

Patch Changes

v2.55.5

Compare Source

Patch Changes

v2.55.4

Compare Source

Patch Changes

v2.55.2

Compare Source

Patch Changes

v2.55.1

Compare Source

Patch Changes

v2.55.0

Compare Source

Minor Changes
Patch Changes

v2.54.6

Compare Source

Patch Changes
  • #​4807 f1ac4480d0c1c6f29bf709f116068e903643ecad Thanks @​jxom! - viem/tempo: Supported calling token .call builders without a Client (restores the pre-2.54 call signature). When the Client is omitted, token must be a TIP20 token id or contract address, and formatted amounts require explicit decimals.

v2.54.5

Compare Source

Patch Changes

v2.54.4

Compare Source

Patch Changes

v2.54.3

Compare Source

Patch Changes

v2.54.2

Compare Source

Patch Changes

v2.54.1

Compare Source

Patch Changes

v2.54.0

Compare Source

Minor Changes
  • #​4767 0def05663277a93e645bc28740a78bfc916810ec Thanks @​jxom! - Breaking (viem/tempo): Changed Tempo token balance and allowance reads to return Amount objects.

    -const balance = await client.token.getBalance({ token })
    -// ^? bigint
    +const balance = await client.token.getBalance({ token })
    +// ^? { amount: bigint; decimals: number; formatted: string }
    
    -const allowance = await client.token.getAllowance({ account, spender, token })
    -// ^? bigint
    +const allowance = await client.token.getAllowance({ account, spender, token })
    +// ^? { amount: bigint; decimals: number; formatted: string }
  • #​4767 0def05663277a93e645bc28740a78bfc916810ec Thanks @​jxom! - Breaking (viem/tempo): Changed Tempo token .call helpers to take the client before their action arguments.

    -Actions.token.transfer.call({ token, to, amount })
    +Actions.token.transfer.call(client, { token, to, amount })
    
    -Actions.token.getBalance.call({ account, token })
    +Actions.token.getBalance.call(client, { account, token })
  • #​4767 0def05663277a93e645bc28740a78bfc916810ec Thanks @​jxom! - Breaking: Changed ERC-20 token actions to resolve token symbols from the Client tokens array instead of built-in chain tokens config.

     import { createPublicClient, http } from 'viem'
     import { mainnet } from 'viem/chains'
    +import { usdc } from 'viem/tokens'
    
    -const client = createPublicClient({ chain: mainnet, transport: http() })
    +const client = createPublicClient({
    +  chain: mainnet,
    +  tokens: [usdc],
    +  transport: http(),
    +})
    
     const balance = await client.token.getBalance({ account, token: 'usdc' })
  • #​4767 0def05663277a93e645bc28740a78bfc916810ec Thanks @​jxom! - Added viem/tokens entrypoint.

Patch Changes

v2.53.1

Compare Source

Patch Changes

v2.52.2

Compare Source

Patch Changes

v2.52.0

Compare Source

Minor Changes

v2.51.3

Compare Source

Patch Changes

v2.51.2

Compare Source

Patch Changes

v2.51.0

Compare Source

Minor Changes
Patch Changes

v2.50.4

Compare Source

Patch Changes

v2.50.3

Compare Source

Patch Changes

v2.49.3

Compare Source

Patch Changes

v2.49.2

Compare Source

Patch Changes

v2.49.0

Compare Source

Minor Changes
Patch Changes
  • #​4608 0e282d69d534e7fc277300260e31c07c4d8cb325 Thanks @​jxom! - viem/tempo: Updated Actions.wallet.send parameters to match the latest wallet RPC schema: renamed value to amount, added an optional memo field (UTF-8, max 32 bytes; rejected for non-TIP-20 tokens), and widened token to also accept curated tokenlist symbols.

    await Actions.wallet.send(client, {
    +  amount: '1.5',
    +  memo: 'thanks',
       to: '0x...',
    -  token: '0x...',
    +  token: 'pathUsd',
    -  value: '1.5',
    })

v2.48.11

Compare Source

Patch Changes

v2.48.8

Compare Source

Patch Changes

v2.48.7

Compare Source

Patch Changes

v2.48.6

Compare Source

Patch Changes

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

Patch Changes

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

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • 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.

@socket-security

socket-security Bot commented Jan 22, 2024

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from 80f821b to 696c0e3 Compare March 20, 2024 21:08
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from 696c0e3 to 58be86a Compare September 11, 2024 07:59
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from 58be86a to 0ea5196 Compare October 8, 2024 05:56
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from eb29e11 to b571fb6 Compare August 10, 2025 06:56
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from b571fb6 to 6f5f4bf Compare August 23, 2025 16:09
@socket-security

socket-security Bot commented Aug 23, 2025

Copy link
Copy Markdown

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Block Low
viem@2.37.4 is a AI-detected potential code anomaly.

Notes: The code appears to be a legitimate, feature-rich Ethereum call utility with support for deployless calls and multicall scheduling. No hardcoded credentials or malicious backdoors are evident. The dynamic require in the error path (ccip.js) is a legitimate pattern for CCIP workflows but represents a dynamic dependency surface that should be monitored. Overall, the module shows standard security-risk characteristics for a blockchain-facing library, with a moderate risk due to complexity and dynamic module loading, but no direct malware indicators.

Confidence: 1.00

Severity: 0.60

From: package.jsonnpm/viem@2.37.4

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/viem@2.37.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.

Block Low
viem@2.37.4 is a AI-detected potential code anomaly.

Notes: The code implements a cross-chain deposit flow with proper validations, artifact reads, and on-chain interactions. There is no evidence of hidden backdoors, data exfiltration, or malware. The main security considerations relate to token approval logic and correct configuration of flags to avoid granting excessive allowances. Overall, the module appears legitimate for a bridge deposit flow, with moderate risk primarily around configuration of approvals and correct handling of gas/fees.

Confidence: 1.00

Severity: 0.60

From: package.jsonnpm/viem@2.37.4

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/viem@2.37.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

@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 3 times, most recently from 4d42ad6 to 46f84f5 Compare September 7, 2025 19:25
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 1e76c53 to c062f30 Compare September 15, 2025 04:09
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 897327b to edf3fe9 Compare September 24, 2025 19:54
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 3 times, most recently from 91c079b to e5164b5 Compare October 7, 2025 03:33
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from a8c3328 to 7857d8c Compare October 18, 2025 15:41
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from 7857d8c to ae844b5 Compare October 25, 2025 20:03
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from ae844b5 to 406267f Compare November 2, 2025 07:45
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 3 times, most recently from 8276609 to 1279155 Compare November 22, 2025 11:45
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from 1279155 to 5235a14 Compare November 27, 2025 22:55
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from 5235a14 to 441b688 Compare December 5, 2025 11:31
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 3 times, most recently from 0e170a1 to 1f93fb7 Compare December 23, 2025 07:41
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from 3199275 to 5c45a63 Compare January 16, 2026 23:25
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from ff3f750 to 2d7f805 Compare February 2, 2026 12:03
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 2c12f54 to f98418a Compare February 19, 2026 03:46
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from e695e43 to e8180ca Compare March 8, 2026 09:47
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from e8180ca to 455b909 Compare March 14, 2026 14:59
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from 455b909 to a5f153b Compare March 31, 2026 18:34
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 816c708 to 703efcb Compare April 19, 2026 07:38
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from a04b263 to aaac978 Compare May 6, 2026 03:51
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 64c3d83 to f7b641c Compare May 17, 2026 11:56
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from f7b641c to 5b32c9d Compare May 23, 2026 08:15
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 20eda55 to e36edc1 Compare June 6, 2026 03:38
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from e36edc1 to bb7d956 Compare June 25, 2026 03:56
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from bb7d956 to 36a3ec8 Compare July 4, 2026 02:57
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 3cb59b0 to 78e28ac Compare July 18, 2026 03:58
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from f10032b to f3dd88e Compare July 30, 2026 07:45
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from f3dd88e to 3299335 Compare August 8, 2026 08:16
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 7479aaa to b7743b4 Compare August 20, 2026 00:10
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from b7743b4 to 9c5cbaa Compare August 30, 2026 08:12
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
renovate Bot force-pushed the renovate/viem-2.x branch from 9c5cbaa to dcff9f7 Compare September 5, 2026 23:22
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.

0 participants