Conversation
Collaborator
|
thanks for the PR, this is in the latest release now! |
pull Bot
pushed a commit
to Dustin4444/opensea-sdk
that referenced
this pull request
Sep 16, 2026
Origin-SHA: 2c84e6e026f87821f153fa2c92d22753d5e99696 ### Minor Changes - cd6e615: Support Arc: offers use the 6-decimal USDC native mirror (0x3600…0000), listings use native USDC, approvals use the OS Ledger conduit. Native (0x0) offer currencies advertised by the API are normalized to the mirror. - 0c24b3e: Support Stable Chain for offers and listings: offers use the 6-decimal USDT0 native mirror (0x779d…3736), listings use native gUSDT0, approvals use the OS Ledger conduit. Native (0x0) offer currencies advertised by the API are normalized to the mirror. ### Patch Changes - Stop forwarding `chain` on `getEventsByCollection` and `getEventsByNFT`; only the account events endpoint documents that filter, and the NFT endpoint already carries the chain in its path. Thanks @Osraka ([opensea-sdk#2011](ProjectOpenSea#2011), fixes [opensea-sdk#2010](ProjectOpenSea#2010)). - cd6e615: Sync OpenAPI spec: add `arc` chain identifier; agent relationships gain `ConfirmAgentRelationshipRequestBody` and optional `counterparty_account_id` addressing, `AgentRelationshipResponse` drops `initiator_address`/`counterparty_address`/`initiated_by`. `revokeAgentRelationship` serializes whichever counterparty identifier is provided (`counterpartyAccountId` or `counterpartyAddress`). - Updated dependencies [fbbbea4] - Updated dependencies [cd6e615] - @opensea/api-types@0.12.0 Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: Osraka <Osraka@users.noreply.github.com>
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
2 participants
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.
Motivation
GetEventsArgs.chainis valid for the account event feed, but the shared args type also lets collection and NFT event calls forward it. Neither endpoint documents that query parameter, and the NFT endpoint already identifies the chain in its path. This can produce an ignored filter or a contradictory URL.Closes #2010
Solution
chainfrom the general, collection, and NFT event query pathschainunchanged for account eventsVerification
npm test(1,239 tests)npm run check-typesnpm run format:checknpm run lint(passes with one pre-existingFunctionwarning intest/provider/seaport-bridge.spec.ts)npm run build