chore: version packages#1006
Open
enbox-release-bot[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Coverage ReportNode (bun test)
Coverage ReportNode coverage not available for this run. Browser Coverage (informational)
Browser coverage is informational only (subset of tests). |
enbox-release-bot
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
16c2e52 to
93bde6a
Compare
enbox-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
93bde6a to
d825c25
Compare
|
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@enbox/agent@0.8.1
Patch Changes
#1005
9b51592Thanks @LiranCohen! - Remove Bun fetch stream buffering workarounds and pass data streams through HTTP and storage paths directly.Updated dependencies [
970aa97,211049b,e781263,9b51592,a2bfa0d]:@enbox/api@0.6.38
Patch Changes
#1005
9b51592Thanks @LiranCohen! - Remove Bun fetch stream buffering workarounds and pass data streams through HTTP and storage paths directly.Updated dependencies [
9b51592]:@enbox/auth@0.6.46
Patch Changes
970aa97,211049b,e781263,9b51592,a2bfa0d]:@enbox/browser@0.3.24
Patch Changes
9b51592]:@enbox/dwn-clients@0.4.6
Patch Changes
#1005
9b51592Thanks @LiranCohen! - Remove Bun fetch stream buffering workarounds and pass data streams through HTTP and storage paths directly.Updated dependencies [
970aa97,211049b,e781263,a2bfa0d]:@enbox/dwn-sdk-js@0.4.1
Patch Changes
#1009
970aa97Thanks @LiranCohen! - fix: convergent tombstones — delete-wins over writes and a canonical-winner lattice among competing deletes. A RecordsDelete now displaces a RecordsWrite regardless of timestamp (the convergent counterpart of the write handler's writes-after-delete rejection), and competing tombstones resolve to one canonical winner on every replica: a prune beats a plain delete regardless of timestamp, and within the same class the newest (messageTimestamp, then CID) wins. Supersession displacement is decided by CID membership rather than timestamp comparison so the retained message survives resumable-task replay. Public behavior change: deleting an already-deleted record now returns 202 when the incoming tombstone wins and 409 Conflict when it is beaten (replication classifies the 409 as a Superseded no-op); 404 is returned only when the record has no messages at all.Records.canPerformDeleteAgainstRecordis removed in favor of the sharedRecords.isDeleteBeatenByExistingTombstonepredicate used by both admission and resumable-task replay.#1011
211049bThanks @LiranCohen! - fix: emit all missing ancestor refs in one IncompleteapplyReplicatedMessagenow layer-batches missing-ancestor dependencies: the incoming message'scontextIdis split into its recordId segments, each segment above the failure-named ancestor is presence-checked against the message store, and a singleIncompletenames every locally-absent ancestor — for both the immediate-parent referential failure and record-chain construction failure — instead of surfacing one ancestry level per retry pass. Deep record chains now resolve in a bounded number of passes regardless of depth. Refs remain recordId selectors and the wire shape is unchanged.#1010
e781263Thanks @LiranCohen! - feat: mark permission records immutableThe permissions protocol now sets
$immutable: trueon therequest,grant, andgrant/revocationpaths. Permission records are write-once by design — a grant is never amended, it is revoked and re-issued — and immutability locks each record's initial-write facts (notably theprotocoltag), which replication fingerprint domains and protocol-scoped shadow filters are computed from. Updates to existing permission records (including tags-only mutations) are now rejected withProtocolAuthorizationImmutableRecordin bothprocessMessageandapplyReplicatedMessage; creating permission records and revoking grants are unaffected.#1012
a2bfa0dThanks @LiranCohen! - fix: carry mutable query-visibility facts (flattenedtag.*andpublished) from the pre-delete latest write onto RecordsDelete tombstone indexes. Without them, tombstones of tagged permission records never match the permission shadow filters and published-record tombstones never matchpublished: truequeries and subscriptions. Immutable record facts keep coming from the initial write, and pruning an already-deleted record carries the existing tombstone's visibility facts forward.@enbox/dwn-server@0.1.10
Patch Changes
#1005
9b51592Thanks @LiranCohen! - Remove Bun fetch stream buffering workarounds and pass data streams through HTTP and storage paths directly.Updated dependencies [
970aa97,211049b,e781263,94b6879,9b51592,a2bfa0d]:@enbox/dwn-sql-store@0.0.26
Patch Changes
#1007
94b6879Thanks @LiranCohen! - fix: always use the S3 Upload helper for streamed object writes.#1005
9b51592Thanks @LiranCohen! - Remove Bun fetch stream buffering workarounds and pass data streams through HTTP and storage paths directly.Updated dependencies [
970aa97,211049b,e781263,a2bfa0d]:@enbox/protocols@0.2.65
Patch Changes
970aa97,211049b,e781263,9b51592,a2bfa0d]:@enbox/electrobun-dwn@0.0.56
Patch Changes
9b51592]: