@seedprotocol/publish 0.7.9-next.1306.g4ff6582 → 0.7.10-next.1344.g3828e8a

package/CHANGELOG.md

@@ -4,6 +4,14 @@ All notable changes to this project will be documented in this file.
 
 ## Unreleased
 
+- `publishItem` (the executor behind `item.publish()`) holds the item until the publish settles, so an item the caller looked up without a hold doesn't unload mid-publish after the SDK's grace period. The publish steps that look an item up themselves take an explicit hold (`Item.find({ hold: true })`), since `find` no longer holds by default.
+- `watchPublishCost` re-estimates after writes to the item's seed, version and property rows, through the SDK's change feed, where one runs (the browser). It compared the loaded property instances' values on every item update, so it missed edits made in another tab or to rows the loaded item hadn't read. In Node, which has no change feed, it still compares the loaded values. The new `watchRows` option replaces how rows are watched.
+- A publish restored from its saved record releases the Item it loads to create attestations once the step finishes or fails, on the multiPublish path too (the direct-EAS path already did). The item stayed held, so it was never unloaded. The lookup that waits for that item now runs one `Item.find` at a time; overlapping lookups each took a hold and only one was returned.
+- `usePublishCostEstimate` keeps showing the last estimate (as `isStale`) when it gets a new Item instance for the same `seedLocalId` and `publishMode`, until the new watcher's first estimate arrives. It showed `null` in between. `watchPublishCost` takes the estimate to start from as `previousEstimate`.
+- `watchPublishCost` retries a failed first estimate once after 5 s (`firstEstimateRetryMs`, 0 turns it off) and stays `isEstimating` until the retry settles. A failed first estimate left `estimate` null until the item changed or `refresh()` was called.
+
+## 0.7.9 (2026-10-22)
+
 - `ensureEasSchemasForItem` registers the schemas of every seed the publish attests from the SDK's `getPublishGraph`, each definition once. It walked each related item's subtree again for every item that referred to it.
 - Recording passes each request's `versionLocalId` to `updateVersionUid` and each attestation's `_attestedValue` to `applyPropertyAttestationUidsFromPublish`, so both update the rows the payload was built from.
 - The data-item steps and `itemNeedsArweaveUpload` read uploads from rows: a publish restored from its saved record no longer loads the item first.
@@ -21,6 +29,24 @@ All notable changes to this project will be documented in this file.
 - A publish saved mid-way through the L1 path (`creatingArweaveTransactions`, `sendingReimbursementRequest`, `pollingForConfirmation`, `uploadingData` or their `Phase2` states) is marked interrupted on restore instead of resuming; publish the item again.
 - The L1-finalize worker no longer restores data item ids that publish 0.7.4 and earlier overwrote with L1 ids. Databases that old are recreated by `@seedprotocol/sdk` (minimum upgrade-from version 0.7.7).
 
+### Commits
+
+#### Breaking
+
+- sdk: recreate databases older than 0.7.7, drop the legacy repairs (8bebbd1c)
+- upload only data items, remove the L1 reimbursement path (51301c01)
+
+#### Fixes
+
+- sdk: record a publish uid on the row whose value was attested (6c43bdb4)
+
+#### Other
+
+- sdk: build publish from rows with one graph walk (T11) (9e67b723)
+- eas, sdk: one EAS model-schema lookup and one model_uids rule (02e732aa)
+- revoke retracted properties after attesting; unpublish revokes the seed first (62759057)
+- Unload items the publish actors reload, and ensureEasSchemas' related items (deacc79f)
+
 ## 0.7.7 (2026-10-18)
 
 ### Commits