feat: adopt the latest Enbox release set (agent 0.8.32 / api 0.6.71) - #184
Merged
Conversation
Bump the @enbox/* set to the newest published versions:
agent 0.8.31 -> 0.8.32 dwn-clients 0.4.22 -> 0.4.23
api 0.6.70 -> 0.6.71 dwn-sdk-js 0.4.15 -> 0.4.16
auth 0.6.77 -> 0.6.78 protocols 0.2.97 -> 0.2.98
browser 0.3.62 -> 0.3.63 connect 0.1.11 -> 0.1.12
(common/crypto/dids already newest.) This adopts the reworked durable
replication engine: cursorless durable pull/push wakes, the coalesced
live-push feed, transport-owned browser wake recovery, the
MessagesSubscribe feed snapshot + empty-log anchor cursor, and
corrupt-checkpoint recovery.
Breaking SyncEvent change: agent 0.8.32 removes the `reconcile:applied`
and `gap:detected` events; `delivery:applied` (now carrying a per-message
descriptor) is the single notification for each freshly admitted remote
message. Migrate use-sync-query-invalidation to it:
- drop the `reconcile:applied` branch in the agent-tenant guard (delivery
events already cover it);
- drop the identity-tenant `reconcile:applied` fallback and its now-unused
queueAllIdentityQueries helper — delivery:applied always carries a
descriptor, so queueIdentityDescriptor gives precise routing without the
conservative refresh-everything path;
- remove the obsolete CID-only-reconciliation test.
Test plan: bun install; bun run build (tsc -b clean); bun run lint
(0 errors); bun run test (779 pass).
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||
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
1 participant
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.
Summary
Adopts the newest published
@enboxrelease set — the agent 0.8.32 durable-replication rework — and migrates the one consumer-facing sync API break.@enbox/agent@enbox/dwn-clients@enbox/api@enbox/dwn-sdk-js@enbox/auth@enbox/protocols@enbox/browser@enbox/connectcommon/crypto/didsalready newest. Single copy of every package in the lockfile (no duplicatedwn-sdk-js).What rides in from the SDK
dwn-sdk-js0.4.16);Breaking
SyncEventchange (the only code migration)agent 0.8.32 removes
reconcile:appliedandgap:detected;delivery:applied— now carrying a per-messagedescriptor— is the single notification for each freshly admitted remote message.use-sync-query-invalidation.tswas the only consumer:reconcile:appliedbranch in the agent-tenant guard (delivery:appliedalready covers it);reconcile:appliedfallback and its now-unusedqueueAllIdentityQuerieshelper —delivery:appliedalways carries adescriptor, soqueueIdentityDescriptorgives precise cache routing without the old conservative "refresh every identity view" path;use-sync-connectivity(link:connectivity-change),use-live-sync-status(repair:failed/link:*,getRemoteSyncStatus/retryRemoteNow), andregistration-repair(repair:failed) all use events that still exist — no change needed.Test plan
bun install— lockfile resolves the 0.8.32 set, single copiesbun run build—tsc -b && vite buildclean (theSyncEventunion change is now type-checked, unlike the olderany-typed agent)bun run lint— 0 errors (pre-existing warnings only, in untouched files)bun run test— 779 passed, 10 pre-existing skipsFollow-ups (out of scope here)
Two sync-timing issues seen in real usage are being investigated separately and may warrant app- or SDK-side fixes: (1) a newly created profile not appearing on dapps until the wallet app is opened on its own (initial push not completing in the connect-only context); (2) empty notes/notebooks briefly after connect/renew in notesd (pull-vs-query race). Notes will follow.