chore(deps): update dependency alchemy-sdk to v2.12.0 - #30
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/alchemy-sdk-2.x-lockfile
branch
from
October 22, 2025 01:32
4bcf9bb to
62e4a97
Compare
renovate
Bot
force-pushed
the
renovate/alchemy-sdk-2.x-lockfile
branch
from
November 18, 2025 22:15
62e4a97 to
3d2c368
Compare
renovate
Bot
force-pushed
the
renovate/alchemy-sdk-2.x-lockfile
branch
from
December 31, 2025 14:51
3d2c368 to
22ed17a
Compare
renovate
Bot
force-pushed
the
renovate/alchemy-sdk-2.x-lockfile
branch
from
January 23, 2026 19:56
22ed17a to
71b4f8d
Compare
renovate
Bot
force-pushed
the
renovate/alchemy-sdk-2.x-lockfile
branch
2 times, most recently
from
February 17, 2026 19:00
71c15e7 to
fa381d3
Compare
renovate
Bot
force-pushed
the
renovate/alchemy-sdk-2.x-lockfile
branch
from
March 5, 2026 17:43
fa381d3 to
957953a
Compare
renovate
Bot
force-pushed
the
renovate/alchemy-sdk-2.x-lockfile
branch
from
April 8, 2026 16:59
957953a to
f0b4360
Compare
renovate
Bot
force-pushed
the
renovate/alchemy-sdk-2.x-lockfile
branch
from
April 29, 2026 13:05
f0b4360 to
e222663
Compare
renovate
Bot
force-pushed
the
renovate/alchemy-sdk-2.x-lockfile
branch
2 times, most recently
from
May 18, 2026 11:00
8fa4c03 to
64d1a4c
Compare
renovate
Bot
force-pushed
the
renovate/alchemy-sdk-2.x-lockfile
branch
from
May 28, 2026 19:35
64d1a4c to
bc868f3
Compare
renovate
Bot
force-pushed
the
renovate/alchemy-sdk-2.x-lockfile
branch
2 times, most recently
from
July 16, 2026 17:34
6b87f54 to
19560d3
Compare
renovate
Bot
force-pushed
the
renovate/alchemy-sdk-2.x-lockfile
branch
from
July 21, 2026 02:07
19560d3 to
2b8f03c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
2.6.2→2.12.0Release Notes
alchemyplatform/alchemy-sdk-js (alchemy-sdk)
v2.11.0Compare Source
Minor Changes
Network.ARB_SEPOLIAenum.v2.10.1Compare Source
Major Changes
Minor Changes
Logobject where theremovedfield was not included in the response.v2.10.0Compare Source
Major Changes
Minor Changes
v2.9.2Compare Source
Major Changes
CoreNamespace.isContractAddress()to easily check if an address is a contract or EOA. The method accepts a string address and returns a boolean value indicating if the given address is a contract address or not.Minor Changes
GetOwnersForContractResponsewas missing thepageKeyfield.v2.9.1Compare Source
Major Changes
Minor Changes
refreshCacheparameter to NFT rarity endpoints to allow users to update stale rarity values.includeCountparameter to getOwnersForContract.v2.9.0Compare Source
Major Changes
NftNamespace.getNftSales()in which there was a typo indecimalfield of theNftSaleFeeDataobject. The field is now correctly nameddecimals, anddecimalis marked deprecated to avoid a breaking change.Minor Changes
CoreNamespace.getTokensForOwner()to handle failures when fetching token metadata.acquiredAtfield for orderedgetNftsForOwnerqueries. Only available when specifyingorderBy: NftOrdering.TRANSFERTIMEin the request.NftSaleMarketplace.BLURmarketplace enum to theNftNamespace.getNftSales()method return.validAtresponse field toNftNamespace.getNftSales().v2.8.3Compare Source
Major Changes
Minor Changes
NotifyNamespacewhen creating webhooks on ETH_SEPOLIA, OPT_GOERLI, and ARB_GOERLI.Wallet.populateTransaction()where the method would never resolve.NftNamespace.getMintedNfts()andNftNamespace.getTransfersForOwner()where the method would always throw an error for certain addresses (#318).v2.8.2Compare Source
Major Changes
Minor Changes
exports.defaultfield to be the last field. This fixed a bug introduced in2.8.1that prevented certain frameworks from building (#313).v2.8.1Compare Source
Major Changes
Minor Changes
moduleResolution: bundlerwhen usingtypescriptatv5.0(#302). Thanks @florrdv!getTransfersForOwner()andgetTransfersForContract()methods in theNftNamespace, where some NFTs would not be returned if the NFT was transferred multiple times.v2.8.0Compare Source
Major Changes
Added PolygonZkEvm Mainnet and Testnet limited support to the sdk
Minor Changes
v2.7.0Compare Source
Major Changes
CustomGraphqlWebhookto be used with theNotifyNamespace. This webhook uses graphql to track any event on every block.Minor Changes
v2.6.3Compare Source
Major Changes
Minor Changes
pageKeyandpageSizeparameter inNftNamespace.getOwnersforNftto allow for pagination of the results.Configuration
📅 Schedule: (UTC)
🚦 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.