Files
github-actions[bot] ff9f84e11a Version packages (#4851)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-04-15 10:06:49 +02:00

32 KiB

@atproto/lex-client

0.0.20

Patch Changes

0.0.19

Patch Changes

  • #4839 b6b231f Thanks @matthieusieben! - Fix typing of delete options to omit body instead of params.

  • #4828 c62651d Thanks @matthieusieben! - Accept legacy blob references in non-strict mode. Legacy blob references (objects with cid and mimeType properties) are now accepted when strict: false, which is the default behavior when strictResponseProcessing is disabled on the Client.

    BREAKING: The allowLegacy option has been removed from the blob schema builder, and legacy blobs are now handled automatically based on the strictness mode: in strict mode they are rejected, and in non-strict mode they are accepted. Consumers should stop passing allowLegacy and rely on strictness configuration instead. Likewise, CLI consumers should stop using the removed --allowLegacyBlobs flag and use the default strict/non-strict behavior.

  • #4835 f6f100c Thanks @matthieusieben! - Use lexParseJsonBytes to convert binary data directly into lex value

  • Updated dependencies [c62651d, f6f100c, c62651d, c62651d, f6f100c]:

    • @atproto/lex-data@0.0.15
    • @atproto/lex-schema@0.0.18
    • @atproto/lex-json@0.0.15

0.0.18

Patch Changes

  • #4779 527f5d4 Thanks @matthieusieben! - Improve handling of XRPC response errors by always using XrpcResponseError errors when upstream server responds with an error status code. Before, XrpcResponseError would only be used if the upstream server responded with a valid XRPC payload (json with error field). Any other response payload (e.g. non-json, invalid "error" payload) would be treated as the upstream server not being able to output a valid XRPC response, and would throw XrpcUpstreamError instead. This change allows to better reflect upstream server errors to downstream services (eg. return a 429 if the upstream server responds with a 429 status code, instead of a 502, even if the response payload is not a valid XRPC error payload).

    XrpcUpstreamError was removed and replaced with XrpcInvalidResponseError to better reflect the intent to those errors (invalid status code, non-json, or invalid payload). XrpcResponseValidationError is a special case of XrpcInvalidResponseError that is thrown when the response does not conform to the expected XRPC output schema.

  • #4788 a99dd58 Thanks @matthieusieben! - Allow XRPC endpoints with no output specified in their schema to output anything.

  • Updated dependencies [527f5d4, c4df84c, 527f5d4, e5e5bcf, ac6bd18, c5c6c7d]:

    • @atproto/lex-schema@0.0.17

0.0.17

Patch Changes

0.0.16

Patch Changes

  • #4714 5a2f884 Thanks @matthieusieben! - Create a specific error class for wrapping unexpected error returned by the fetchHandler. This allows to better distinguish unexpected internal server errors (due to implementation encountering an unexpected case) from potentially transient errors that occur when performing network HTTP requests.

  • Updated dependencies [3dc3791, 3dc3791, 3dc3791, 3dc3791, 112b159, 3dc3791, 3dc3791]:

    • @atproto/lex-schema@0.0.15

0.0.15

Patch Changes

  • #4688 52834ab Thanks @matthieusieben! - Update error management to be more aligned with the way errors work in @atproto/xrpc and @atproto/xrpc-server

  • #4688 52834ab Thanks @matthieusieben! - Add dedicated XrpcInvalidResponseError error for responses that don't match the schema

  • #4688 52834ab Thanks @matthieusieben! - Rename matchesSchema to matchesSchemaErrors to make it more explicit what is being matched when called on an XRPC "result" (that could either represent a success or failure)

  • Updated dependencies [52834ab, f7c2610, 52834ab, 52834ab, 52834ab, 52834ab, 52834ab]:

    • @atproto/lex-schema@0.0.14
    • @atproto/lex-data@0.0.13
    • @atproto/lex-json@0.0.13

0.0.14

Patch Changes

0.0.13

Patch Changes

0.0.12

Patch Changes

0.0.11

Patch Changes

0.0.10

Patch Changes

0.0.9

Patch Changes

0.0.8

Patch Changes

0.0.7

Patch Changes

  • #4501 2f78893 Thanks @matthieusieben! - breaking: Use a record type (com.example.record.Main) instead of a record schema type (typeof com.example.record.$defs.main) as the generic parameter for ListRecord.

  • Updated dependencies [2f78893, 2f78893, 2f78893, 2f78893]:

    • @atproto/lex-data@0.0.6
    • @atproto/lex-schema@0.0.7
    • @atproto/lex-json@0.0.6

0.0.6

Patch Changes

0.0.5

Patch Changes

0.0.4

Patch Changes

  • Updated dependencies [693784c]:
    • @atproto/lex-data@0.0.3
    • @atproto/lex-json@0.0.3
    • @atproto/lex-schema@0.0.4

0.0.3

Patch Changes

0.0.2

Patch Changes

  • Updated dependencies [23c271f]:
    • @atproto/lex-schema@0.0.2

0.0.1

Patch Changes