Releases: alchemyplatform/alchemy-sdk-js
Releases · alchemyplatform/alchemy-sdk-js
v3.2.0
3.2.0
Major Changes
- Added support for Polygon Amoy network via the
Network.MATIC_AMOY
enum.
v3.1.2
v3.1.0
v3.0.0
3.0.0
Major Changes
- For a full list of changes to V3 from V2, please visit: https://docs.alchemy.com/reference/alchemy-sdk-v2-to-v3-migration-guide. There, you can also find the API reference for v2 endpoints as well. V3 primarily involves changes to use the V3 NFT API.
v2.11.0
v2.10.1
2.10.1
Major Changes
Minor Changes
- Fixed a bug in the
Log
object where theremoved
field was not included in the response.
v2.10.0
2.10.0
Major Changes
- Add support for Base
Minor Changes
v2.9.2
2.9.2
Major Changes
- Added a new method
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
- Fixed a bug where
GetOwnersForContractResponse
was missing thepageKey
field.
v2.9.1
2.9.1
Major Changes
Minor Changes
- Add the
refreshCache
parameter to NFT rarity endpoints to allow users to update stale rarity values. - Add the
includeCount
parameter to getOwnersForContract.
v2.9.0
2.9.0
Major Changes
- Fixed a bug with in
NftNamespace.getNftSales()
in which there was a typo indecimal
field of theNftSaleFeeData
object. The field is now correctly nameddecimals
, anddecimal
is marked deprecated to avoid a breaking change.
Minor Changes
- Added redundancy to
CoreNamespace.getTokensForOwner()
to handle failures when fetching token metadata. - Added support for the
acquiredAt
field for orderedgetNftsForOwner
queries. Only available when specifyingorderBy: NftOrdering.TRANSFERTIME
in the request. - Added the
NftSaleMarketplace.BLUR
marketplace enum to theNftNamespace.getNftSales()
method return. - Added support for the
validAt
response field toNftNamespace.getNftSales()
.