fix(deps): update dependency @rainbow-me/rainbowkit to ^0.12.0 #52
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.8.0
->^0.12.0
Release Notes
rainbow-me/rainbowkit (@rainbow-me/rainbowkit)
v0.12.18
Compare Source
Patch Changes
144809c
: Upgraded minimumwagmi
peer dependency to0.12.19
for improved WalletConnect v2 support.v0.12.17
Compare Source
Patch Changes
e1fd3df
: Fixed an issue with MetaMask Mobile's connector that blocked WalletConnect pairingsv0.12.16
Compare Source
Patch Changes
6af1db7
: Upgraded minimumwagmi
peer dependency to0.12.18
for improved WalletConnect v2 support.v0.12.15
: rainbow-me/[email protected]Compare Source
Patch Changes
e2b1072
: Support for WalletConnect v2 is now standard in RainbowKit.Every dApp that relies on WalletConnect now needs to obtain a
projectId
from WalletConnect Cloud. This is absolutely free and only takes a few minutes.This must be completed before WalletConnect v1 bridge servers are shutdown on June 28, 2023.
Upgrade RainbowKit and provide the
projectId
togetDefaultWallets
and individual RainbowKit wallet connectors like the following:You can read the full migration guide here.
We are continuing support for
0.12.x
in case your dApp has not yet upgraded to wagmi v1 and RainbowKit v1.It is recommended that
0.12.x
dApps begin to upgrade to wagmi v1, as stability improvements for WalletConnect v2 will only be included in future versions of wagmi.Advanced options
If a dApp requires supporting a legacy wallet that has not yet migrated to WalletConnect v2, the WalletConnect version can be overriden.
Once the WalletConnect v1 servers are shutdown, a custom bridge server is required.
Reference the docs for additional supported options.
v0.12.14
Compare Source
Patch Changes
865175f
: Upgraded minimumethers
peer dependency to^5.6.8
.v0.12.13
Compare Source
Patch Changes
0f8e87e
: Improved extension store supportRainbowKit wallet connectors now support multiple browser extension download URLs, and RainbowKit will automatically direct users to the appropriate extension store.
Users will also experience an improved download flow for extensions, including support for Arc, Opera, and Safari browsers.
dApps that utilize the
Custom Wallets
API can reference the updated docs here.6eab54d
: Detecting MetaMask inwindow.ethereum.providers
for wallets that support theethereum.providers
standard.Overriding Wagmi's
getProvider
logic for MetaMask to ensure that MetaMask is preferred when available, and RainbowKit's MetaMask button continues to act as a fallback for users that rely on wallets that overridewindow.ethereum
.v0.12.12
Compare Source
Patch Changes
ab051b9
: Support foroptions
customization forwalletConnectWallet
Example usage
Reference the docs for additional supported options.
v0.12.11
Compare Source
v0.12.10
Compare Source
v0.12.9
Compare Source
Patch Changes
361bb39
: Phantom SupportExample usage
82376f0
: Rabby SupportExample usage
7c9e580
: Trust Wallet SupportThe
trustWallet
wallet connector now includes support for the Trust Wallet browser extension.Example usage
0127559
: XDEFI Wallet SupportExample usage
v0.12.8
Compare Source
Patch Changes
aef9643
: Support for WalletConnect CloudprojectId
Every dApp that relies on WalletConnect now needs to obtain a
projectId
from WalletConnect Cloud. This is absolutely free and only takes a few minutes.RainbowKit will enable WalletConnect v2 for supported wallets when
projectId
is specified. IfprojectId
is unspecified, RainbowKit will quietly prefer WalletConnect v1.This must be completed before WalletConnect v1 bridge servers are shutdown on June 28, 2023.
Provide the
projectId
togetDefaultWallets
and individual RainbowKit wallet connectors like the following:v0.12.7
Compare Source
Patch Changes
4ef5c51
: Fixed an issue that caused mobile WalletConnect redirects for signing request hooks to fail in Wagmi 0.12.xv0.12.6
Compare Source
Patch Changes
d35809e
: AmendedrainbowWallet
connector extension support and URLsImproved UI flow for wallet connectors that don't specify
extension.instructions
v0.12.5
Compare Source
Patch Changes
2b4ede4
: Zerion SupportExample usage
6a01368
: Taho SupportExample usage
936b523
: OKX Wallet SupportExample usage
7f669bd
: Dawn Wallet SupportExample usage
v0.12.4
Compare Source
Patch Changes
9b93f56
: AddedsafeWallet
connector to support Safe Apps. dApps that rely ongetDefaultWallets
will adopt this behavior automatically. dApps that rely on the Custom Wallet List should addsafeWallet
alongsideinjectedWallet
.v0.12.3
Compare Source
Patch Changes
e7f1bec
:injectedWallet
now has a friendlier name and iconfe4f356
: RainbowKit dApps that usegetDefaultWallets
orinjectedWallet
will now more eagerly display the fallbackinjectedWallet
connector to better support dApp Browsers when a branded connector is unavailable.v0.12.2
Compare Source
Patch Changes
2a1d230
: FixedshimDisconnect
wallet connector option to maintain default Wagmi disconnect behavior whenshimDisconnect
is unspecified. RainbowKit wallet connectors now also accept allInjectedConnectorOptions
options.429a3c7
: Improvements to RainbowKit UX on iPadv0.12.1
Compare Source
Patch Changes
865175f
: Upgraded minimumethers
peer dependency to^5.6.8
.v0.12.0
Compare Source
Minor Changes
9838acf
: The wagmi peer dependency has been updated to0.12.x
.RainbowKit has adopted the
WalletConnectLegacyConnector
connector inwagmi
for continued WalletConnect v1 support. Support for WalletConnect v2 andWalletConnectConnector
will soon be available as a patch release, without breaking changes.Wallets will be transitioned automatically in future releases.
Follow the steps below to migrate.
1. Upgrade RainbowKit and
wagmi
to their latest versionv0.11.1
Compare Source
Patch Changes
924ae82
: Bumped minimumwagmi
version to0.11.7
Added
baseGoerli
chain support5e233ea
: Addedbsc
andbscTestnet
chain supportv0.11.0
Compare Source
Minor Changes
1876ba0
: The wagmi peer dependency has been updated to0.11.x
.The minimum TypeScript version is now
4.9.4
Follow the steps below to migrate.
If you use
wagmi
hooks in your application, you will need to check if your application has been affected by the breaking changes inwagmi
.You can see their migration guide here.
v0.10.0
Compare Source
Minor Changes
355402b
: The wagmi peer dependency has been updated to0.10.x
.Follow the steps below to migrate.
If you use
wagmi
hooks in your application, you will need to check if your application has been affected by the breaking changes inwagmi
.You can see their migration guide here.
v0.9.0
Compare Source
Minor Changes
49f0ec9
: The wagmi peer dependency has been updated to0.9.x
.Follow the steps below to migrate.
If you use
wagmi
hooks in your application, you will need to check if your application has been affected by the breaking changes inwagmi
.You can see their migration guide here.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.