Skip to content

Releases: sanity-io/client

v6.1.0

15 May 12:13
Compare
Choose a tag to compare

6.1.0 (2023-05-15)

Features

Bug Fixes

  • apply resultSourceMap parameter only to queries (#225) (dac8ea6)

This release is also available on:

v6.0.1

03 May 15:35
Compare
Choose a tag to compare

6.0.1 (2023-05-03)

Introducing Content Source Maps

Note

Content Source Maps are available for select Sanity enterprise customers. Contact our sales team for more information.

Content Source Maps are an optional layer of contextual metadata sent with queries to enable use cases such as Visual Editing, tracing content lineage, and more. Our implementation of Content Source Maps are based on an open standard posted on GitHub, and you can read the API documentation here. To get started with Content Source Maps, check out the documentation in the README file.

Bug Fixes


This release is also available on:

v6.0.0

03 May 13:50
284c845
Compare
Choose a tag to compare

6.0.0 (2023-05-03)

⚠ BREAKING CHANGES

  • useCdn is now set to true by default. Our CDN ensures your content has reliably, world-wide delivery by caching queries made from your front-end. If you require fresh data for every query, perhaps for testing purposes, add useCdn: false to your configuration.
  • Client will now automatically retry all GET/HEAD requests as well as queries if the server responds with a 429, 502 or 503 status code - as well as on socket/DNS errors. Previously, the client would immediately throw an error. If you have application-level retry code, you should either disable the retrying in the client by passing {maxRetries: 0}, or remove the custom retry code and potentially alter the retryDelay and maxRetries options to match your wanted behavior.

The migration guide outlines every breaking change and how to migrate your code

Introducing Content Source Maps

Note

Content Source Maps are available for select Sanity enterprise customers. Contact our sales team for more information.

Content Source Maps are an optional layer of contextual metadata sent with queries to enable use cases such as Visual Editing, tracing content lineage, and more. Our implementation of Content Source Maps are based on an open standard posted on GitHub, and you can read the API documentation here. To get started with Content Source Maps, check out the documentation in the README file.

Features

  • add automatic retrying of 429, 502, 503 (#199)

Bug Fixes

  • make useCdn use true by default (#191)
  • undeprecate request() (#205)

This release is also available on:

v5.4.2

03 Apr 21:02
Compare
Choose a tag to compare

5.4.2 (2023-04-03)

Bug Fixes

  • mutate: reflect support for providing transaction id in typings (#187) (b7ad302)
  • mutate: serialize clientless patches correctly (#186) (b635dff)

This release is also available on:

v5.4.1

30 Mar 12:26
Compare
Choose a tag to compare

5.4.1 (2023-03-30)

Bug Fixes


This release is also available on:

v5.4.0

28 Mar 15:23
Compare
Choose a tag to compare

5.4.0 (2023-03-28)

Features


This release is also available on:

v5.3.2

23 Mar 06:54
Compare
Choose a tag to compare

5.3.2 (2023-03-23)

Bug Fixes

  • declare File for envs without lib.dom (#175) (1e9cb5e)

v5.3.1

22 Mar 19:27
Compare
Choose a tag to compare

5.3.1 (2023-03-22)

Bug Fixes

  • deps: update dependency @sanity/eventsource to v5 (#169) (1cda138)

This release is also available on:

v5.3.0

13 Mar 16:45
Compare
Choose a tag to compare

5.3.0 (2023-03-13)

Features

  • include mutation error items in error message (#148) (193f45e)

Bug Fixes


This release is also available on:

v5.2.2

21 Feb 00:57
Compare
Choose a tag to compare

5.2.2 (2023-02-21)

Bug Fixes

  • deps: update devdependencies (non-major) (#132) (0acb16b)

This release is also available on: