Skip to content

Commit b642fda

Browse files
ryanioclaude
andcommitted
Release v0.14.1
Origin-SHA: 18afcce1a666d3a93a06d86934d836ec0dee4943 ### Patch Changes - 749dc16: Sync OpenAPI spec. `DropDeployResponse` gains `from`, the address that must send the deploy transaction. Drop mint and cross-chain mint document a retryable 503, which, like every 429, now declares the `Retry-After` response header (seconds, integer), and the self-mint item create and update operations document a 422 for a contract that does not support self-mint. Drop operation and schema descriptions now cover each drop type's lifecycle, the deployable drop and token type combinations, stage rules, reveal, the allowlist file format, media filename rules and when to use PUT or PATCH for items. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
1 parent 481e181 commit b642fda

5 files changed

Lines changed: 227 additions & 53 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,11 @@
11
# @opensea/api-types
22

3+
## 0.14.1
4+
5+
### Patch Changes
6+
7+
- 749dc16: Sync OpenAPI spec. `DropDeployResponse` gains `from`, the address that must send the deploy transaction. Drop mint and cross-chain mint document a retryable 503, which, like every 429, now declares the `Retry-After` response header (seconds, integer), and the self-mint item create and update operations document a 422 for a contract that does not support self-mint. Drop operation and schema descriptions now cover each drop type's lifecycle, the deployable drop and token type combinations, stage rules, reveal, the allowlist file format, media filename rules and when to use PUT or PATCH for items.
8+
39
## 0.14.0
410

511
### Minor Changes

0 commit comments

Comments
 (0)