chore(deps): update dependency @api3/chains to v4 #1916
Merged
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:
^3.5.1
->^4.1.0
Release Notes
api3dao/chains (@api3/chains)
v4.1.0
Compare Source
New Features
Optional Viem config environment variable support
viemConfig.chains()
now (optionally) supports adding additionalrpcUrls
values using specific environment variables. These environment variables take the form ofAPI3_CHAINS_HTTP_RPC_URL_${toUpperSnakeCase(chain.alias)}
. When a matching value is detected, a newenvironment
key is added torpcUrls
.NOTE: you can still access the existing provided
default
andpublic
values, as these are not affected.For example, the new
rpcUrls
object will look like:{ default: { http: ['https://existing-rpc.xyz'] }, public: { http: ['https://existing-rpc.xyz'] }, + environment: { http: ['https://custom-rpc.xyz'] }, }
v4.0.0
Compare Source
Breaking changes
providerUrl is now a providers array
providerUrl
has been replaced with aproviders
array to allow for more than 1 RPC provider. Eachprovider
object has the following interface:NOTE:
default
rpcUrl
is optional to allow for values that may contain a sensitive API key in the URLYou can migrate existing
providerUrl
code with the following snippetNew Features
Viem Config support
You can now generate chains compatible with Viem/Wagmi
Updated Chains
In all cases, the
alias
value is unchangedRSK
renamed toRootstock
and has a new default RPC URLRSK Testnet
renamed toRootstock Testnet
and has a new default RPC URLArbitrum
renamed toArbitrum One
BSC
renamed toBNB Smart Chain
BSC Testnet
renamed toBNB Smart Chain Testnet
Miscellaneous
zkSync hardhat config overrides
zkSync (and zkSync Testnet) require additional fields for use with Hardhat. These fields are now included with the respective chain definitions and used when generating the Hardhat config.
See issue: https://github.com/api3dao/chains/issues/55 and the chain definitions for more information
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Mend Renovate. View repository job log here.