chore: version packages

[enbox-release-bot]

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.35

Patch Changes

• #1476 00dafdf Thanks @LiranCohen! - Authenticate protocol configurations used for remote encryption-policy resolution and record artifacts returned through app-facing remote query, read, and initial subscription snapshot calls, bind record results to the original request filter, and verify inline or streamed record bytes against their signed CID and size. Remote protocol definitions used for encryption policy must now be signed directly by the target DID. Anonymous subscriptions now use the current transport request shape, and lazy read-only records reject data from a different record version.

  These checks authenticate returned artifacts; they do not prove result completeness or freshness because DWN query replies do not yet carry a tenant-authenticated state commitment. RecordsCount replies carry no signed artifacts, so their aggregate values remain assertions by the remote DWN. Initial RecordsSubscribe snapshots are verified, but subsequent live events remain outside this response-verification boundary.

  Streamed reads are authenticated at successful end-of-stream, so callers can observe chunks before the final CID check completes. Integrity-sensitive consumers that cannot tolerate an unauthenticated prefix must buffer the stream through successful completion before using its bytes.

• Updated dependencies [00dafdf, 2a4223a, 9511e65, d257e04, 8b0dc99]:

  • @enbox/dwn-sdk-js@0.4.19
  • @enbox/connect@0.1.15
  • @enbox/dwn-clients@0.4.26

@enbox/api@0.6.74

Patch Changes

• #1476 00dafdf Thanks @LiranCohen! - Authenticate protocol configurations used for remote encryption-policy resolution and record artifacts returned through app-facing remote query, read, and initial subscription snapshot calls, bind record results to the original request filter, and verify inline or streamed record bytes against their signed CID and size. Remote protocol definitions used for encryption policy must now be signed directly by the target DID. Anonymous subscriptions now use the current transport request shape, and lazy read-only records reject data from a different record version.

  These checks authenticate returned artifacts; they do not prove result completeness or freshness because DWN query replies do not yet carry a tenant-authenticated state commitment. RecordsCount replies carry no signed artifacts, so their aggregate values remain assertions by the remote DWN. Initial RecordsSubscribe snapshots are verified, but subsequent live events remain outside this response-verification boundary.

  Streamed reads are authenticated at successful end-of-stream, so callers can observe chunks before the final CID check completes. Integrity-sensitive consumers that cannot tolerate an unauthenticated prefix must buffer the stream through successful completion before using its bytes.

• #1472 33dba16 Thanks @LiranCohen! - fix: carry protocol roles through typed point reads and deletes, including lazy record data reads

• Updated dependencies [00dafdf, 2a4223a, 9511e65, d257e04, 8b0dc99]:

  • @enbox/dwn-sdk-js@0.4.19
  • @enbox/agent@0.8.35
  • @enbox/auth@0.6.81
  • @enbox/dwn-clients@0.4.26

@enbox/auth@0.6.81

Patch Changes

• Updated dependencies [00dafdf, 2a4223a, 9511e65, d257e04, 8b0dc99]:
  • @enbox/dwn-sdk-js@0.4.19
  • @enbox/agent@0.8.35
  • @enbox/connect@0.1.15
  • @enbox/dwn-clients@0.4.26

@enbox/browser@0.3.66

Patch Changes

• Updated dependencies [00dafdf, 8291bcd, 2a4223a, 9511e65, d257e04, 8b0dc99, 33dba16]:
  • @enbox/dwn-sdk-js@0.4.19
  • @enbox/agent@0.8.35
  • @enbox/api@0.6.74
  • @enbox/protocols@0.2.101
  • @enbox/auth@0.6.81
  • @enbox/connect@0.1.15

@enbox/cli@0.1.27

Patch Changes

• Updated dependencies [00dafdf, 33dba16]:
  • @enbox/agent@0.8.35
  • @enbox/api@0.6.74
  • @enbox/auth@0.6.81
  • @enbox/connect@0.1.15

@enbox/connect@0.1.15

Patch Changes

• Updated dependencies [00dafdf, 2a4223a, 9511e65, d257e04, 8b0dc99]:
  • @enbox/dwn-sdk-js@0.4.19

@enbox/dwn-clients@0.4.26

Patch Changes

• Updated dependencies [00dafdf, 2a4223a, 9511e65, d257e04, 8b0dc99]:
  • @enbox/dwn-sdk-js@0.4.19

@enbox/dwn-sdk-js@0.4.19

Patch Changes

• #1476 00dafdf Thanks @LiranCohen! - Authenticate protocol configurations used for remote encryption-policy resolution and record artifacts returned through app-facing remote query, read, and initial subscription snapshot calls, bind record results to the original request filter, and verify inline or streamed record bytes against their signed CID and size. Remote protocol definitions used for encryption policy must now be signed directly by the target DID. Anonymous subscriptions now use the current transport request shape, and lazy read-only records reject data from a different record version.

  These checks authenticate returned artifacts; they do not prove result completeness or freshness because DWN query replies do not yet carry a tenant-authenticated state commitment. RecordsCount replies carry no signed artifacts, so their aggregate values remain assertions by the remote DWN. Initial RecordsSubscribe snapshots are verified, but subsequent live events remain outside this response-verification boundary.

  Streamed reads are authenticated at successful end-of-stream, so callers can observe chunks before the final CID check completes. Integrity-sensitive consumers that cannot tolerate an unauthenticated prefix must buffer the stream through successful completion before using its bytes.

• #1471 2a4223a Thanks @LiranCohen! - Fix RecordsSubscribe authorization lifetime. Open subscriptions now re-fetch
  referenced Records.Read grants and revalidate embedded author-delegate grants and
  protocol-role membership before each matching event is delivered. A deleted,
  revoked, or expired referenced grant, or a removed role assignment, closes the subscription with
  RecordsSubscribeDeliveryAuthorizationFailed; a transient non-DWN revalidation
  failure closes it with the retryable RecordsSubscribeDeliveryFailed code.

• #1480 9511e65 Thanks @LiranCohen! - Reject protocol definitions that combine $role and $recordLimit on the same path. Record-limit projection can hide stored records, so allowing those hidden records to remain role capabilities would make visible membership disagree with authorization.

  Previously installed definitions and role records are not rewritten. Retire an affected protocol URI, install the corrected definition under a new protocol URI, and migrate only intended role assignments.

• #1469 d257e04 Thanks @LiranCohen! - fix: independently enforce target-DWN authorization after validating an author-delegated RecordsRead grant

• #1479 8b0dc99 Thanks @LiranCohen! - Reject protocol definitions that allow anyone to create or squash a $role record. Role assignments now require an authorized issuer whose authority is rooted in the tenant, an explicit grant or delegate, an ancestor relationship, or an existing role.

  Previously installed definitions and role records are not rewritten. Applications that installed an open role-assignment path should retire that protocol URI, install a corrected definition under a new URI, migrate authorized assignments, and stop relying on records issued under the unsafe definition.

@enbox/dwn-server@0.1.34

Patch Changes

• Updated dependencies [00dafdf, 2a4223a, 9511e65, d257e04, 8b0dc99]:
  • @enbox/dwn-sdk-js@0.4.19
  • @enbox/dwn-clients@0.4.26
  • @enbox/dwn-sql-store@0.0.44

@enbox/dwn-sql-store@0.0.44

Patch Changes

• Updated dependencies [00dafdf, 2a4223a, 9511e65, d257e04, 8b0dc99]:
  • @enbox/dwn-sdk-js@0.4.19

@enbox/local-node@0.0.21

Patch Changes

• Updated dependencies [00dafdf]:
  • @enbox/agent@0.8.35
  • @enbox/dwn-server@0.1.34

@enbox/protocols@0.2.101

Patch Changes

• #1470 8291bcd Thanks @LiranCohen! - Remove SocialGraphProtocol, StatusProtocol, and ListsProtocol from the shipped catalog together with their definitions, data types, codecs, and JSON Schemas. The removed Social Graph definition allowed anyone to create a friend role record, while current role invocation accepts a matching role recipient without independently binding the role to a trusted issuer. A caller could therefore self-assign friend authority and reach friend-gated data in protocols composed with that role. Profile no longer composes with Social Graph and no longer exposes PrivateNoteData or the friend-gated privateNote path.

  This removal does not change engine role verification, uninstall definitions, revoke existing role records, or migrate stored data. Applications that installed these protocols should stop treating their role-gated records as confidential, install a corrected protocol under a new URI, migrate and re-encrypt sensitive records, and retire the old records. No replacement or compatibility aliases are provided.

• Updated dependencies [00dafdf, 2a4223a, 9511e65, d257e04, 8b0dc99, 33dba16]:

  • @enbox/dwn-sdk-js@0.4.19
  • @enbox/api@0.6.74

@enbox/electrobun-dwn@0.0.92

Patch Changes

• Updated dependencies [00dafdf, 8291bcd, 33dba16]:
  • @enbox/agent@0.8.35
  • @enbox/api@0.6.74
  • @enbox/protocols@0.2.101
  • @enbox/auth@0.6.81
  • @enbox/dwn-server@0.1.34

[LiranCohen]

Please hold this version PR until #1476 merges. That PR corrects the still-pending Social Graph removal release note to disclose the role self-mint security rationale and migration guidance; the Changesets action should refresh this PR afterward.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud