Skip to content

fix(deps): update dependency viem to v2#33

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

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

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Dec 16, 2024 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

Release Notes

wevm/viem (viem)

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

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 tempoTestnet → tempoModerato. The old export is deprecated but still available as an alias.
    • (Breaking): Renamed reward.start → reward.distribute: Renamed for distributing rewards (no longer supports streaming).
    • (Breaking): Renamed reward.getTotalPerSecond → reward.getGlobalRewardPerToken: Returns the global reward per token value instead of per-second rate.
    • (Breaking): Renamed reward.watchRewardScheduled → reward.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.stablecoinExchange → Address.stablecoinDex.
    • (Breaking): Renamed Abis.stablecoinExchange → Abis.stablecoinDex.
    • Added dex.cancelStale action to cancel stale orders from restricted makers.
    • Added salt parameter to token.create.
Patch Changes

v2.43.5

Compare Source

Patch Changes

v2.43.4

Compare Source

Patch Changes

v2.43.3

Compare Source

Patch Changes

v2.43.2

Compare Source

Patch Changes

v2.43.1

Compare Source

Patch Changes

v2.43.0

Compare Source

Minor Changes

  • #​4107 b423fc17eba4f9f0648f72f5358a8e5ed9d5f092 Thanks @​tmm! - Added experimental named tuple support for contract-related actions and utilities.

  • #​4147 734d99d9da4b76f9aa985a800213b4ba581607df Thanks @​jxom! - Added first-class support and extension for Tempo.

    Attaching a Tempo chain to your client grants your transaction actions with Tempo superpowers like batched calls and external fee payer capabilities.

    import { createClient, http } from "viem";
import { privateKeyToAccount } from "viem/accounts";
import { tempoTestnet } from "viem/chains";

const client = createClient({
  account: privateKeyToAccount("0x…"),
  chain: tempoTestnet.extend({
    feeToken: "0x20c00000000000000000000000000000000000fa",
  }),
  transport: http(),
});

const receipt = client.sendTransactionSync({
  calls: [
    { data: "0x…", to: "0x…" },
    { data: "0x…", to: "0x…" },
    { data: "0x…", to: "0x…" },
  ],
  feePayer: privateKeyToAccount("0x…"),
});

    You can also use Tempo Actions to call to enshrined protocol features like the Stablecoin Token Factory:

    import { createClient, http } from "viem";
import { privateKeyToAccount } from "viem/accounts";
import { tempoTestnet } from "viem/chains";
import { tempoActions } from "viem/tempo";

const client = createClient({
  account: privateKeyToAccount("0x…"),
  chain: tempoTestnet,
  transport: http(),
}).extend(tempoActions());

const { receipt, token } = await client.token.createSync({
  currency: "USD",
  name: "My Company USD",
  symbol: "CUSD",
});
Patch Changes

v2.42.1

Compare Source

Patch Changes

v2.42.0

Compare Source

Minor Changes

  • #​4134 d9d666beeccf748157d1292849f5a0d18768baf7 Thanks @​mikelxc! - Added EntryPoint v0.9 support for Account Abstraction (ERC-4337).

    • Added entryPoint09Abi and entryPoint09Address constants
    • Added '0.9' to EntryPointVersion type
    • Added UserOperation<'0.9'> with new paymasterSignature field for parallelizable paymaster signing
    • Updated getUserOperationHash to support v0.9 (uses EIP-712 typed data like v0.8)
    • Updated toPackedUserOperation to handle paymasterSignature
    • Updated prepareUserOperation type definitions for v0.9
Patch Changes

v2.41.2

[Compare Source](https://redirect.gith

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
Copy link
Copy Markdown

socket-security Bot commented Dec 16, 2024 •
edited
Loading

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@​0.9.8 ⏵ 1.1.0100 +1100100 +288100
Added@​noble/​ciphers@​1.3.010010010091100
Addedox@​0.9.31001009997100
Updatedviem@​1.21.4 ⏵ 2.37.5100 +610010097 +1100

View full report

@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from cf7e599 to cd495a4 Compare July 28, 2025 15:05
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 502f706 to af382dc Compare August 10, 2025 09:50
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from af382dc to 8402be8 Compare August 19, 2025 11:34
@socket-security
Copy link
Copy Markdown

socket-security Bot commented Aug 19, 2025 •
edited
Loading

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.5 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.json → npm/viem@2.37.5

ℹ 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.5. 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.5 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.json → npm/viem@2.37.5

ℹ 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.5. 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 from 8402be8 to 0005bfa Compare August 28, 2025 00:09
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 3 times, most recently from fbe5514 to 65956d6 Compare September 10, 2025 11:10
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from fa1f9a5 to d9ff5d1 Compare September 23, 2025 11:40
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 3 times, most recently from 02700f8 to 26c6d81 Compare October 6, 2025 06:52
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from bb41331 to 6ebad9f Compare October 15, 2025 23:10
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 6ebad9f to 1b43908 Compare October 17, 2025 07:00
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 15c43c3 to e63dcca Compare October 31, 2025 14:02
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from e63dcca to d85ccc0 Compare November 4, 2025 18:40
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 3 times, most recently from a76ce78 to b848e09 Compare November 21, 2025 02:37
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from d478898 to 189a133 Compare December 3, 2025 15:06
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 189a133 to bef0617 Compare December 5, 2025 22:33
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 1ec0f6a to 8a34d82 Compare December 20, 2025 02:58
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from b393973 to 60be96f Compare December 31, 2025 18:45
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from f2208fd to 2c8cacc Compare January 12, 2026 02:09
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 2c8cacc to fbbf91f Compare January 16, 2026 16:38
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from dc964ac to b58e2b0 Compare February 2, 2026 02:26
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 3 times, most recently from f84c6c5 to 0dc661e Compare February 18, 2026 07:07
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 6476f4b to 9231992 Compare March 5, 2026 16:53
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 6f3f935 to 1c94452 Compare March 15, 2026 02:16
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from be58d2f to 53ec085 Compare March 24, 2026 10:59
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 3 times, most recently from ce22f45 to e96aabc Compare April 13, 2026 03:04
@renovate renovate Bot force-pushed the renovate/viem-2.x branch 2 times, most recently from 1f1f763 to 281fe15 Compare April 18, 2026 06:56
@renovate
fix(deps): update dependency viem to v2
3b0b38b 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate Bot force-pushed the renovate/viem-2.x branch from 281fe15 to 3b0b38b Compare April 24, 2026 03:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants