Skip to content

Update dependency viem to v2.55.2#19

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

Update dependency viem to v2.55.2#19
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/viem-2.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Sep 2, 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) 2.7.92.55.2 age confidence

Release Notes

wevm/viem (viem)

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

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](https://redirect.github.com/wevm/viem/comp

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 Sep 2, 2024

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedisows@​1.0.3 ⏵ 1.0.71001007582100
Updatedabitype@​1.0.0 ⏵ 1.1.0100 +1100100 +190100
Added@​noble/​ciphers@​1.3.010010010091100
Addedox@​0.9.31001009997100
Updatedviem@​2.7.9 ⏵ 2.37.4100 +610010097 +1100

View full report

@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.0 fix(deps): update dependency viem to v2.21.1 Sep 3, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from ce45226 to 7a766f0 Compare September 8, 2024 08:42
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.1 fix(deps): update dependency viem to v2.21.2 Sep 8, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.2 fix(deps): update dependency viem to v2.21.3 Sep 10, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from 7a766f0 to b02b23e Compare September 13, 2024 05:49
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.3 fix(deps): update dependency viem to v2.21.4 Sep 13, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from b02b23e to cc2156e Compare September 14, 2024 11:48
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.4 fix(deps): update dependency viem to v2.21.5 Sep 14, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.5 fix(deps): update dependency viem to v2.21.6 Sep 15, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.6 fix(deps): update dependency viem to v2.21.7 Sep 18, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from cc2156e to 698a5b7 Compare September 21, 2024 14:49
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.7 fix(deps): update dependency viem to v2.21.9 Sep 21, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.9 fix(deps): update dependency viem to v2.21.10 Sep 24, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from 698a5b7 to a016272 Compare September 27, 2024 08:51
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.10 fix(deps): update dependency viem to v2.21.14 Sep 27, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.14 fix(deps): update dependency viem to v2.21.15 Oct 1, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from a016272 to 637b294 Compare October 4, 2024 05:07
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.15 fix(deps): update dependency viem to v2.21.16 Oct 4, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.16 fix(deps): update dependency viem to v2.21.17 Oct 6, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.17 fix(deps): update dependency viem to v2.21.18 Oct 7, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from 637b294 to 9193609 Compare October 11, 2024 05:27
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.18 fix(deps): update dependency viem to v2.21.19 Oct 11, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from 9193609 to 01c8acb Compare October 13, 2024 05:09
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.19 fix(deps): update dependency viem to v2.21.21 Oct 13, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from 01c8acb to 5cbcf65 Compare October 14, 2024 08:40
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.21 fix(deps): update dependency viem to v2.21.22 Oct 14, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.22 fix(deps): update dependency viem to v2.21.25 Oct 18, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from 5cbcf65 to 7cc8578 Compare October 19, 2024 08:53
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.25 fix(deps): update dependency viem to v2.21.27 Oct 19, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.36 fix(deps): update dependency viem to v2.21.37 Nov 2, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from 662dbd8 to 36317b8 Compare November 4, 2024 17:59
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.37 fix(deps): update dependency viem to v2.21.38 Nov 4, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.38 fix(deps): update dependency viem to v2.21.40 Nov 7, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from 36317b8 to c44224f Compare November 9, 2024 06:01
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.40 fix(deps): update dependency viem to v2.21.41 Nov 9, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.41 fix(deps): update dependency viem to v2.21.42 Nov 10, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.42 fix(deps): update dependency viem to v2.21.43 Nov 11, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.43 fix(deps): update dependency viem to v2.21.44 Nov 13, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from c44224f to 7def432 Compare November 16, 2024 08:38
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.44 fix(deps): update dependency viem to v2.21.45 Nov 16, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from 7def432 to 1062e6a Compare November 20, 2024 23:54
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.45 fix(deps): update dependency viem to v2.21.47 Nov 20, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.47 fix(deps): update dependency viem to v2.21.48 Nov 22, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from 1062e6a to 91bf97b Compare November 25, 2024 20:59
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.48 fix(deps): update dependency viem to v2.21.49 Nov 25, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.49 fix(deps): update dependency viem to v2.21.50 Nov 28, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from 91bf97b to cbf6566 Compare November 30, 2024 02:49
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.50 fix(deps): update dependency viem to v2.21.51 Nov 30, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.51 fix(deps): update dependency viem to v2.21.53 Dec 3, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from cbf6566 to ed21b7c Compare December 11, 2024 05:38
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.53 fix(deps): update dependency viem to v2.21.54 Dec 11, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from ed21b7c to c2fab29 Compare December 16, 2024 01:56
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.54 fix(deps): update dependency viem to v2.21.55 Dec 16, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from c2fab29 to b0de267 Compare December 24, 2024 05:58
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.55 fix(deps): update dependency viem to v2.21.56 Dec 24, 2024
@renovate renovate Bot changed the title fix(deps): update dependency viem to v2.21.56 fix(deps): update dependency viem to v2.21.57 Dec 26, 2024
@renovate
renovate Bot force-pushed the renovate/viem-2.x-lockfile branch from b0de267 to 551635f Compare January 1, 2025 11:26
@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

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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