Skip to content

chore(deps): bump the lifi-depts group across 1 directory with 5 updates - #25

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/lifi-depts-a7c20535a0
Open

chore(deps): bump the lifi-depts group across 1 directory with 5 updates#25
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/lifi-depts-a7c20535a0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 21, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the lifi-depts group with 5 updates in the / directory:

Package From To
@bigmi/client 0.9.0 0.10.1
@lifi/sdk 4.1.0 4.4.0
@lifi/sdk-provider-bitcoin 4.0.2 4.0.6
@lifi/sdk-provider-ethereum 4.0.3 4.0.9
@lifi/sdk-provider-solana 4.0.2 4.0.6

Updates @bigmi/client from 0.9.0 to 0.10.1

Release notes

Sourced from @​bigmi/client's releases.

@​bigmi/client@​0.10.1

Patch Changes

  • #67 3532b51 Thanks @​arentant! - Prevent UniSat reconnect from opening the extension popup on page load.

  • #70 f427391 Thanks @​chybisov! - Stop the Binance, Bitget, OKX and OneKey connectors from opening their wallet extension on page load. connect() now honours isReconnecting and verifies authorization through passive getAccounts() access, matching the UniSat, Xverse and Unhosted connectors. Bitget and OKX additionally confirm the extension still exposes an account instead of trusting the connected storage shim alone, and getAccounts() returns an empty list rather than throwing when no account is exposed. All five connectors now report an account-less extension as ConnectorNotConnectedError instead of mislabelling it a user rejection: the try wraps only requestAccounts(), the one step a user can actually reject. This also fixes OKX persisting a disconnected shim — and so silently disabling its own auto-reconnect for good — when a reconnect found no accounts.

  • #66 8da5d88 Thanks @​yasha-meursault! - Fix reconnect leaving a stale connection stub after reload. On the first successful reconnection the connections map is now rebuilt from scratch instead of copying the map rehydrated from storage under the previous session's connector uid, and current points at the freshly reconnected connector. When no connector reconnects, connections and current are reset alongside status: 'disconnected'. Matches wagmi's behavior.

  • #69 7ff01b5 Thanks @​chybisov! - Stop reconnect from clearing a connection established by a concurrent connect() call. Reconnect runs on mount and polls for a wallet provider for up to 5s, so a user can connect manually while it is still in flight; the no-connector-reconnected reset now only applies when the store is still in the reconnecting/connecting state reconnect put it in. Matches wagmi's behavior.

@​bigmi/client@​0.10.0

Minor Changes

  • #62 3569fc2 Thanks @​chybisov! - chore: migrate the toolchain to TypeScript 7

    Bump the typescript devDependency from 6.x to 7.x (the native compiler) across the workspace, and bump tsdown 0.22.3 → 0.22.7 so its peer range accepts typescript@^7.

    This is a build-time-only change with no integration impact: typescript is a devDependency (never a peer/runtime dependency), so consumers' own TypeScript version is untouched, and .d.ts/.js emit is handled by tsdown (Rolldown + OXC isolated declarations), not tsc. tsc --noEmit type-checks cleanly on TS 7 with zero source changes, and the public type surface is semantically identical (a rebuild only reformats declaration whitespace/comments via the newer rolldown-plugin-dts printer). Safe to ship as a minor.

Patch Changes

Changelog

Sourced from @​bigmi/client's changelog.

0.10.1

Patch Changes

  • #67 3532b51 Thanks @​arentant! - Prevent UniSat reconnect from opening the extension popup on page load.

  • #70 f427391 Thanks @​chybisov! - Stop the Binance, Bitget, OKX and OneKey connectors from opening their wallet extension on page load. connect() now honours isReconnecting and verifies authorization through passive getAccounts() access, matching the UniSat, Xverse and Unhosted connectors. Bitget and OKX additionally confirm the extension still exposes an account instead of trusting the connected storage shim alone, and getAccounts() returns an empty list rather than throwing when no account is exposed. All five connectors now report an account-less extension as ConnectorNotConnectedError instead of mislabelling it a user rejection: the try wraps only requestAccounts(), the one step a user can actually reject. This also fixes OKX persisting a disconnected shim — and so silently disabling its own auto-reconnect for good — when a reconnect found no accounts.

  • #66 8da5d88 Thanks @​yasha-meursault! - Fix reconnect leaving a stale connection stub after reload. On the first successful reconnection the connections map is now rebuilt from scratch instead of copying the map rehydrated from storage under the previous session's connector uid, and current points at the freshly reconnected connector. When no connector reconnects, connections and current are reset alongside status: 'disconnected'. Matches wagmi's behavior.

  • #69 7ff01b5 Thanks @​chybisov! - Stop reconnect from clearing a connection established by a concurrent connect() call. Reconnect runs on mount and polls for a wallet provider for up to 5s, so a user can connect manually while it is still in flight; the no-connector-reconnected reset now only applies when the store is still in the reconnecting/connecting state reconnect put it in. Matches wagmi's behavior.

0.10.0

Minor Changes

  • #62 3569fc2 Thanks @​chybisov! - chore: migrate the toolchain to TypeScript 7

    Bump the typescript devDependency from 6.x to 7.x (the native compiler) across the workspace, and bump tsdown 0.22.3 → 0.22.7 so its peer range accepts typescript@^7.

    This is a build-time-only change with no integration impact: typescript is a devDependency (never a peer/runtime dependency), so consumers' own TypeScript version is untouched, and .d.ts/.js emit is handled by tsdown (Rolldown + OXC isolated declarations), not tsc. tsc --noEmit type-checks cleanly on TS 7 with zero source changes, and the public type surface is semantically identical (a rebuild only reformats declaration whitespace/comments via the newer rolldown-plugin-dts printer). Safe to ship as a minor.

Patch Changes

Commits
  • 62c1e68 chore: version packages (#68)
  • 27c0cea chore(deps): update dependencies and clear transitive advisories (#72)
  • f427391 fix(client): avoid interactive reconnect for remaining connectors (#70)
  • 7ff01b5 fix(client): keep concurrent connect() alive across reconnect (#69)
  • 3532b51 fix(client): avoid interactive UniSat reconnect (#67)
  • 8da5d88 fix(client): drop stale connections on reconnect (#66)
  • fd9887c chore: version packages (#64)
  • 3569fc2 chore: adopt TypeScript 7 and refresh toolchain (#62)
  • See full diff in compare view

Updates @lifi/sdk from 4.1.0 to 4.4.0

Release notes

Sourced from @​lifi/sdk's releases.

@​lifi/sdk@​4.4.0

Minor Changes

  • fd1e9b5 Thanks @​chybisov! - Add Stellar (STL) ecosystem support. Introduces the @lifi/sdk-provider-stellar package — address validation, Federation resolution, SAC-based balance reads, and route execution via StellarStepExecutor — and registers ChainType.STL in the SDK client's chain fetching so Stellar chains and RPC URLs load.

    Execution signs the backend-generated Soroban envelope with the connected wallet, submits it over Stellar RPC, waits for on-chain confirmation, then tracks the transfer through the LI.FI status API. Because a Stellar envelope embeds the sender's account sequence number and a short-lived set of timebounds, the provider always requests a freshly built transaction immediately before signing rather than reusing the one attached to the quote. SAC allowances are granted first when a step requires one, and the approval is confirmed on-chain before the route transaction is requested.

    PrepareTransactionTask gains a shouldRefetchTransaction hook. It defaults to the previous behaviour — fetch only when the step carries no transaction request — and the Stellar task overrides it, because a Stellar envelope embeds the sender's sequence number and cannot be reused.

    StellarProviderOptions.horizonUrl is gone — nothing read it — and StellarWallet.signAuthEntry is now optional, because the router routes use source-account auth and the SDK never calls it. The provider also exports DEFAULT_NETWORK_PASSPHRASE, and refuses to sign when the connected wallet's network disagrees with the configured one.

@​lifi/sdk@​4.3.0

Minor Changes

  • #431 08b54da Thanks @​chybisov! - Remove the getWalletBalances action and client method — the underlying /wallets/{address}/balances API endpoint is deprecated. Use getTokenBalances/getTokenBalancesByChain to fetch balances directly from RPCs instead.

Patch Changes

  • #435 d8b7adb Thanks @​chybisov! - Bump runtime dependencies: @​lifi/types to 17.86.0 (sdk), viem to 2.55.8 (ethereum), and @​mysten/sui to 2.22.1 (sui).

@​lifi/sdk@​4.2.0

Minor Changes

  • #433 0990a5d Thanks @​chmanie! - Forward routeOptions.svmPriorityFeeLevel (NORMAL | FAST | ULTRA) to /advanced/stepTransaction for Solana steps, letting integrators pick the priority-fee tier used when building Solana transactions.

@​lifi/sdk-provider-stellar@​4.2.0

Minor Changes

  • fd1e9b5 Thanks @​chybisov! - Add Stellar (STL) ecosystem support. Introduces the @lifi/sdk-provider-stellar package — address validation, Federation resolution, SAC-based balance reads, and route execution via StellarStepExecutor — and registers ChainType.STL in the SDK client's chain fetching so Stellar chains and RPC URLs load.

    Execution signs the backend-generated Soroban envelope with the connected wallet, submits it over Stellar RPC, waits for on-chain confirmation, then tracks the transfer through the LI.FI status API. Because a Stellar envelope embeds the sender's account sequence number and a short-lived set of timebounds, the provider always requests a freshly built transaction immediately before signing rather than reusing the one attached to the quote. SAC allowances are granted first when a step requires one, and the approval is confirmed on-chain before the route transaction is requested.

    PrepareTransactionTask gains a shouldRefetchTransaction hook. It defaults to the previous behaviour — fetch only when the step carries no transaction request — and the Stellar task overrides it, because a Stellar envelope embeds the sender's sequence number and cannot be reused.

    StellarProviderOptions.horizonUrl is gone — nothing read it — and StellarWallet.signAuthEntry is now optional, because the router routes use source-account auth and the SDK never calls it. The provider also exports DEFAULT_NETWORK_PASSPHRASE, and refuses to sign when the connected wallet's network disagrees with the configured one.

Patch Changes

@​lifi/sdk-provider-sui@​4.1.6

Patch Changes

@​lifi/sdk-provider-sui@​4.1.5

Patch Changes

... (truncated)

Changelog

Sourced from @​lifi/sdk's changelog.

4.4.0

Minor Changes

  • fd1e9b5 Thanks @​chybisov! - Add Stellar (STL) ecosystem support. Introduces the @lifi/sdk-provider-stellar package — address validation, Federation resolution, SAC-based balance reads, and route execution via StellarStepExecutor — and registers ChainType.STL in the SDK client's chain fetching so Stellar chains and RPC URLs load.

    Execution signs the backend-generated Soroban envelope with the connected wallet, submits it over Stellar RPC, waits for on-chain confirmation, then tracks the transfer through the LI.FI status API. Because a Stellar envelope embeds the sender's account sequence number and a short-lived set of timebounds, the provider always requests a freshly built transaction immediately before signing rather than reusing the one attached to the quote. SAC allowances are granted first when a step requires one, and the approval is confirmed on-chain before the route transaction is requested.

    PrepareTransactionTask gains a shouldRefetchTransaction hook. It defaults to the previous behaviour — fetch only when the step carries no transaction request — and the Stellar task overrides it, because a Stellar envelope embeds the sender's sequence number and cannot be reused.

    StellarProviderOptions.horizonUrl is gone — nothing read it — and StellarWallet.signAuthEntry is now optional, because the router routes use source-account auth and the SDK never calls it. The provider also exports DEFAULT_NETWORK_PASSPHRASE, and refuses to sign when the connected wallet's network disagrees with the configured one.

4.3.0

Minor Changes

  • #431 08b54da Thanks @​chybisov! - Remove the getWalletBalances action and client method — the underlying /wallets/{address}/balances API endpoint is deprecated. Use getTokenBalances/getTokenBalancesByChain to fetch balances directly from RPCs instead.

Patch Changes

  • #435 d8b7adb Thanks @​chybisov! - Bump runtime dependencies: @​lifi/types to 17.86.0 (sdk), viem to 2.55.8 (ethereum), and @​mysten/sui to 2.22.1 (sui).

4.2.0

Minor Changes

  • #433 0990a5d Thanks @​chmanie! - Forward routeOptions.svmPriorityFeeLevel (NORMAL | FAST | ULTRA) to /advanced/stepTransaction for Solana steps, letting integrators pick the priority-fee tier used when building Solana transactions.
Commits
  • 8d227ae chore: version packages (#443)
  • a8c2600 chore(release): migrate to Changesets v3 and changesets/action v2, fix versio...
  • fd1e9b5 feat(stellar): add Stellar (STL) SDK provider (#427)
  • 64260f2 chore: version packages (#436)
  • d8b7adb chore: bump packages (#435)
  • 08b54da feat: remove getWalletBalances action for deprecated /balances endpoint (#431)
  • 0cf5417 chore: version packages (#434)
  • 0990a5d feat(sdk): forward svmPriorityFeeLevel to stepTransaction for Solana steps (#...
  • 1de76f9 chore: bump packages (#429)
  • fe9b9be chore: migrate to TypeScript 7 (#428)
  • Additional commits viewable in compare view

Updates @lifi/sdk-provider-bitcoin from 4.0.2 to 4.0.6

Release notes

Sourced from @​lifi/sdk-provider-bitcoin's releases.

@​lifi/sdk-provider-bitcoin@​4.0.6

Patch Changes

@​lifi/sdk-provider-bitcoin@​4.0.5

Patch Changes

@​lifi/sdk-provider-bitcoin@​4.0.4

Patch Changes

@​lifi/sdk-provider-bitcoin@​4.0.3

Patch Changes

  • #429 1de76f9 Thanks @​chybisov! - Bump runtime dependencies: viem to 2.55.1 (ethereum), @​bigmi/core to 0.9.0 (bitcoin), and @​mysten/sui to 2.20.3 (sui).
Changelog

Sourced from @​lifi/sdk-provider-bitcoin's changelog.

4.0.6

Patch Changes

4.0.5

Patch Changes

4.0.4

Patch Changes

4.0.3

Patch Changes

  • #429 1de76f9 Thanks @​chybisov! - Bump runtime dependencies: viem to 2.55.1 (ethereum), @​bigmi/core to 0.9.0 (bitcoin), and @​mysten/sui to 2.20.3 (sui).
Commits

Updates @lifi/sdk-provider-ethereum from 4.0.3 to 4.0.9

Release notes

Sourced from @​lifi/sdk-provider-ethereum's releases.

@​lifi/sdk-provider-ethereum@​4.0.9

Patch Changes

  • #438 d12b5b6 Thanks @​chmanie! - Fix getAccountCode treating a code-less account as a failed RPC lookup (viem's getCode returns undefined for both), suppressing native EIP-2612 permits for every plain EOA. Permit-supporting tokens now route through callDiamondWithEIP2612Signature rather than callDiamondWithPermit2, skipping the approve(permit2).

    Fix Permit2 reverting for EIP-7702 delegated accounts. Permit2 verifies code-bearing signers via EIP-1271, where acceptance is implementation-specific, so the signer is now probed with a read-only isValidSignature call — only accounts that reject it fall back to approve + execute. The probe gates the standard transaction flow only — relayer-settled steps keep the spender they already used.

    isSafeWallet no longer queries the Safe Transaction Service for an address with no on-chain code. Its code-less short-circuit was unreachable while getAccountCode conflated "no code" with "RPC failed", so an undeployed or counterfactual Safe now resolves as a non-Safe wallet instead of falling through to the API. This surfaces through resolveTransactionHash, which returns such a value as a plain transaction hash rather than tracking it as a Safe signature.

  • Updated dependencies [fd1e9b5]:

@​lifi/sdk-provider-ethereum@​4.0.8

Patch Changes

  • #435 d8b7adb Thanks @​chybisov! - Bump runtime dependencies: @​lifi/types to 17.86.0 (sdk), viem to 2.55.8 (ethereum), and @​mysten/sui to 2.22.1 (sui).

  • Updated dependencies [d8b7adb, 08b54da]:

@​lifi/sdk-provider-ethereum@​4.0.7

Patch Changes

@​lifi/sdk-provider-ethereum@​4.0.6

Patch Changes

  • #429 1de76f9 Thanks @​chybisov! - Bump runtime dependencies: viem to 2.55.1 (ethereum), @​bigmi/core to 0.9.0 (bitcoin), and @​mysten/sui to 2.20.3 (sui).

@​lifi/sdk-provider-ethereum@​4.0.5

Patch Changes

  • #425 7ebebde Thanks @​chybisov! - Handle wallets that resolve signTypedData with a nullish or empty signature instead of rejecting (#424). The EIP-2612 native permit flow now falls back to the Permit2/standard approval path instead of crashing later with TypeError: Cannot read properties of null (reading 'slice'), and the other signing flows (API permits, relayed intents, Permit2 messages) throw a descriptive SignatureRejected error. Permit lookups also ignore stored entries without a usable signature.

@​lifi/sdk-provider-ethereum@​4.0.4

Patch Changes

Changelog

Sourced from @​lifi/sdk-provider-ethereum's changelog.

4.0.9

Patch Changes

  • #438 d12b5b6 Thanks @​chmanie! - Fix getAccountCode treating a code-less account as a failed RPC lookup (viem's getCode returns undefined for both), suppressing native EIP-2612 permits for every plain EOA. Permit-supporting tokens now route through callDiamondWithEIP2612Signature rather than callDiamondWithPermit2, skipping the approve(permit2).

    Fix Permit2 reverting for EIP-7702 delegated accounts. Permit2 verifies code-bearing signers via EIP-1271, where acceptance is implementation-specific, so the signer is now probed with a read-only isValidSignature call — only accounts that reject it fall back to approve + execute. The probe gates the standard transaction flow only — relayer-settled steps keep the spender they already used.

    isSafeWallet no longer queries the Safe Transaction Service for an address with no on-chain code. Its code-less short-circuit was unreachable while getAccountCode conflated "no code" with "RPC failed", so an undeployed or counterfactual Safe now resolves as a non-Safe wallet instead of falling through to the API. This surfaces through resolveTransactionHash, which returns such a value as a plain transaction hash rather than tracking it as a Safe signature.

  • Updated dependencies [fd1e9b5]:

4.0.8

Patch Changes

  • #435 d8b7adb Thanks @​chybisov! - Bump runtime dependencies: @​lifi/types to 17.86.0 (sdk), viem to 2.55.8 (ethereum), and @​mysten/sui to 2.22.1 (sui).

  • Updated dependencies [d8b7adb, 08b54da]:

4.0.7

Patch Changes

4.0.6

Patch Changes

  • #429 1de76f9 Thanks @​chybisov! - Bump runtime dependencies: viem to 2.55.1 (ethereum), @​bigmi/core to 0.9.0 (bitcoin), and @​mysten/sui to 2.20.3 (sui).

4.0.5

Patch Changes

  • #425 7ebebde Thanks @​chybisov! - Handle wallets that resolve signTypedData with a nullish or empty signature instead of rejecting (#424). The EIP-2612 native permit flow now falls back to the Permit2/standard approval path instead of crashing later with TypeError: Cannot read properties of null (reading 'slice'), and the other signing flows (API permits, relayed intents, Permit2 messages) throw a descriptive SignatureRejected error. Permit lookups also ignore stored entries without a usable signature.

4.0.4

Patch Changes

Commits

Updates @lifi/sdk-provider-solana from 4.0.2 to 4.0.6

Release notes

Sourced from @​lifi/sdk-provider-solana's releases.

@​lifi/sdk-provider-solana@​4.0.6

Patch Changes

@​lifi/sdk-provider-solana@​4.0.5

Patch Changes

  • #409 f6f8865 Thanks @​chybisov! - Fix Solana Jito bundle execution (EMB-462). The executor now routes by the shape of the backend's transactionRequest.data — an array is submitted via sendBundle, a string via sendTransaction — instead of inferring it from the signed-transaction count. The Jito-capable RPC probe now uses getBundleStatuses instead of getTipAccounts, so providers such as Helius (which support sendBundle/getBundleStatuses but not getTipAccounts) are correctly detected and bundles submit successfully.

  • Updated dependencies [d8b7adb, 08b54da]:

@​lifi/sdk-provider-solana@​4.0.4

Patch Changes

@​lifi/sdk-provider-solana@​4.0.3

Patch Changes

Changelog

Sourced from @​lifi/sdk-provider-solana's changelog.

4.0.6

Patch Changes

4.0.5

Patch Changes

  • #409 f6f8865 Thanks @​chybisov! - Fix Solana Jito bundle execution (EMB-462). The executor now routes by the shape of the backend's transactionRequest.data — an array is submitted via sendBundle, a string via sendTransaction — instead of inferring it from the signed-transaction count. The Jito-capable RPC probe now uses getBundleStatuses instead of getTipAccounts, so providers such as Helius (which support sendBundle/getBundleStatuses but not getTipAccounts) are correctly detected and bundles submit successfully.

  • Updated dependencies [d8b7adb, 08b54da]:

4.0.4

Patch Changes

4.0.3

Patch Changes

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 21, 2026
@vercel

vercel Bot commented Jul 21, 2026 •
edited
Loading

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
good-wallet-v2 Ignored Ignored Preview Aug 4, 2026 10:47am

Request Review

@dependabot dependabot Bot changed the title Bump the lifi-depts group with 5 updates Bump the lifi-depts group across 1 directory with 5 updates Jul 28, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/lifi-depts-a7c20535a0 branch 3 times, most recently from 27cbf2f to 7e29967 Compare July 30, 2026 05:40
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/lifi-depts-a7c20535a0 branch 2 times, most recently from d15ad71 to aa55777 Compare August 5, 2026 15:40
@dependabot dependabot Bot changed the title Bump the lifi-depts group across 1 directory with 5 updates chore(deps): bump the lifi-depts group across 1 directory with 5 updates Aug 5, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/lifi-depts-a7c20535a0 branch 13 times, most recently from 42b4e77 to e05a045 Compare August 12, 2026 18:04
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/lifi-depts-a7c20535a0 branch from e05a045 to 3bf3289 Compare August 14, 2026 15:22
@dependabot
chore(deps): bump the lifi-depts group across 1 directory with 5 updates
6503e3b 
Bumps the lifi-depts group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@bigmi/client](https://github.com/lifinance/bigmi/tree/HEAD/packages/client) | `0.9.0` | `0.10.1` |
| [@lifi/sdk](https://github.com/lifinance/sdk/tree/HEAD/packages/sdk) | `4.1.0` | `4.4.0` |
| [@lifi/sdk-provider-bitcoin](https://github.com/lifinance/sdk/tree/HEAD/packages/sdk-provider-bitcoin) | `4.0.2` | `4.0.6` |
| [@lifi/sdk-provider-ethereum](https://github.com/lifinance/sdk/tree/HEAD/packages/sdk-provider-ethereum) | `4.0.3` | `4.0.9` |
| [@lifi/sdk-provider-solana](https://github.com/lifinance/sdk/tree/HEAD/packages/sdk-provider-solana) | `4.0.2` | `4.0.6` |



Updates `@bigmi/client` from 0.9.0 to 0.10.1
- [Release notes](https://github.com/lifinance/bigmi/releases)
- [Changelog](https://github.com/lifinance/bigmi/blob/main/packages/client/CHANGELOG.md)
- [Commits](https://github.com/lifinance/bigmi/commits/@bigmi/client@0.10.1/packages/client)

Updates `@lifi/sdk` from 4.1.0 to 4.4.0
- [Release notes](https://github.com/lifinance/sdk/releases)
- [Changelog](https://github.com/lifinance/sdk/blob/main/packages/sdk/CHANGELOG.md)
- [Commits](https://github.com/lifinance/sdk/commits/@lifi/sdk@4.4.0/packages/sdk)

Updates `@lifi/sdk-provider-bitcoin` from 4.0.2 to 4.0.6
- [Release notes](https://github.com/lifinance/sdk/releases)
- [Changelog](https://github.com/lifinance/sdk/blob/main/packages/sdk-provider-bitcoin/CHANGELOG.md)
- [Commits](https://github.com/lifinance/sdk/commits/@lifi/sdk-provider-bitcoin@4.0.6/packages/sdk-provider-bitcoin)

Updates `@lifi/sdk-provider-ethereum` from 4.0.3 to 4.0.9
- [Release notes](https://github.com/lifinance/sdk/releases)
- [Changelog](https://github.com/lifinance/sdk/blob/main/packages/sdk-provider-ethereum/CHANGELOG.md)
- [Commits](https://github.com/lifinance/sdk/commits/@lifi/sdk-provider-ethereum@4.0.9/packages/sdk-provider-ethereum)

Updates `@lifi/sdk-provider-solana` from 4.0.2 to 4.0.6
- [Release notes](https://github.com/lifinance/sdk/releases)
- [Changelog](https://github.com/lifinance/sdk/blob/main/packages/sdk-provider-solana/CHANGELOG.md)
- [Commits](https://github.com/lifinance/sdk/commits/@lifi/sdk-provider-solana@4.0.6/packages/sdk-provider-solana)

---
updated-dependencies:
- dependency-name: "@bigmi/client"
  dependency-version: 0.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: lifi-depts
- dependency-name: "@lifi/sdk"
  dependency-version: 4.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: lifi-depts
- dependency-name: "@lifi/sdk-provider-bitcoin"
  dependency-version: 4.0.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: lifi-depts
- dependency-name: "@lifi/sdk-provider-ethereum"
  dependency-version: 4.0.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: lifi-depts
- dependency-name: "@lifi/sdk-provider-solana"
  dependency-version: 4.0.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: lifi-depts
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/lifi-depts-a7c20535a0 branch from 3bf3289 to 6503e3b Compare August 17, 2026 18:29
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

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants