build(deps-dev): bump alchemy-sdk from 2.2.3 to 2.9.1 in /animation_url

[dependabot]

Bumps alchemy-sdk from 2.2.3 to 2.9.1.

Release notes

Sourced from alchemy-sdk's releases.

v2.9.0

2.9.0

Major Changes

• Fixed a bug with in NftNamespace.getNftSales() in which there was a typo in decimal field of the NftSaleFeeData object. The field is now correctly named decimals, and decimal 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 ordered getNftsForOwner queries. Only available when specifying orderBy: NftOrdering.TRANSFERTIME in the request.
• Added the NftSaleMarketplace.BLUR marketplace enum to the NftNamespace.getNftSales() method return.
• Added support for the validAt response field to NftNamespace.getNftSales().

v2.8.3

2.8.3

Major Changes

Minor Changes

• Fixed a bug with NotifyNamespace when creating webhooks on ETH_SEPOLIA, OPT_GOERLI, and ARB_GOERLI.
• Fixed a bug with Wallet.populateTransaction() where the method would never resolve.
• Fixed a bug with NftNamespace.getMintedNfts() and NftNamespace.getTransfersForOwner() where the method would always throw an error for certain addresses (#318).

v2.8.2

2.8.2

Major Changes

Minor Changes

• Moved the exports.default field to be the last field. This fixed a bug introduced in 2.8.1 that prevented certain frameworks from building (#313).

v2.8.1

2.8.1

Major Changes

Minor Changes

• Fixed a bug where the SDK was not compatible with moduleResolution: bundler when using typescript at v5.0(#302). Thanks @​florrdv!
• Fixed a bug with getTransfersForOwner() and getTransfersForContract() methods in the NftNamespace, where some NFTs would not be returned if the NFT was transferred multiple times.

v2.8.0

2.8.0

Major Changes

Added PolygonZkEvm Mainnet and Testnet support to the sdk

... (truncated)

Changelog

Sourced from alchemy-sdk's changelog.

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.

2.9.0

Major Changes

• Fixed a bug with in NftNamespace.getNftSales() in which there was a typo in decimal field of the NftSaleFeeData object. The field is now correctly named decimals, and decimal 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 ordered getNftsForOwner queries. Only available when specifying orderBy: NftOrdering.TRANSFERTIME in the request.
• Added the NftSaleMarketplace.BLUR marketplace enum to the NftNamespace.getNftSales() method return.
• Added support for the validAt response field to NftNamespace.getNftSales().

2.8.3

Major Changes

Minor Changes

• Fixed a bug with NotifyNamespace when creating webhooks on ETH_SEPOLIA, OPT_GOERLI, and ARB_GOERLI.
• Fixed a bug with Wallet.populateTransaction() where the method would never resolve.
• Fixed a bug with NftNamespace.getMintedNfts() and NftNamespace.getTransfersForOwner() where the method would always throw an error for certain addresses (#318).

2.8.2

Major Changes

Minor Changes

• Moved the exports.default field to be the last field. This fixed a bug introduced in 2.8.1 that prevented certain frameworks from building (#313).

2.8.1

Major Changes

Minor Changes

• Fixed a bug where the SDK was not compatible with moduleResolution: bundler when using typescript at v5.0(#302). Thanks @​florrdv!
• Fixed a bug with getTransfersForOwner() and getTransfersForContract() methods in the NftNamespace, where some NFTs would not be returned if the NFT was transferred multiple times.

2.8.0

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by alchemy-team, a new releaser for alchemy-sdk since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #890.