Skip to content

Releases: cozy/cozy-client

v57.2.0

04 Mar 09:48
Compare
Choose a tag to compare

57.2.0 (2025-03-04)

Features

  • Add ifMatch option to FileCollection methods (1e60e3c)

v57.1.0

27 Feb 10:21
Compare
Choose a tag to compare

57.1.0 (2025-02-27)

Features

  • Improve store query performance for id queries (449c7cd)

v57.0.0

25 Feb 14:01
Compare
Choose a tag to compare

57.0.0 (2025-02-25)

Features

  • Add a option to create a "shared drive" sharing (d78caee)
  • Add FileCollection.getSharedDrivesDirectoryOrCreate (c7a36cf)
  • Manage rules for shared drive sharing (542761e)
  • Remove deprecated SharingCollection.share method (fdafda8)
  • Remove sharingType argument from getSharingRules (7571509)
  • Rename getOrCreateSharedDrivesDirectory (92aa9e4)

BREAKING CHANGES

  • SharingCollection.share method has been removed. Use
    SharingCollection.create method.

v56.0.0

25 Feb 08:16
Compare
Choose a tag to compare

56.0.0 (2025-02-25)

Features

  • Remove fsnative model and mobile cordova helpers (ed23fda)

BREAKING CHANGES

  • fsnative model has been removed. readMobileFile and
    doMobileUpload methods have been removed on file model. If you still
    have them in an app, you can safely remove the code.

v55.1.0

20 Feb 17:05
Compare
Choose a tag to compare

55.1.0 (2025-02-20)

Bug Fixes

  • Promise.all do not complete if a promise is rejected (54d748f)

Features

  • Ensure previous replication are done (46bd57b)

v55.0.0

19 Feb 15:50
Compare
Choose a tag to compare

55.0.0 (2025-02-19)

Bug Fixes

  • Always use response body as FetchError reason (d664bc0)

Features

  • Add option to always throw fetch errors (f05d997)

BREAKING CHANGES

  • The reason attribute of non-JSON fetch errors is no
    longer a string composed of the server response status and status
    text.

    We used to have 2 different kinds of values for the reason attribute
    of FetchError built in CozyStackClient:

    • a string representation of the response body sent by the server
      (which may contain details about what when wrong, especially for 400
      status responses) for JSON requests
    • a string composed of the server response status and status text for
      non-JSON requests

    In the non-JSON request situation, we lose information by not using
    the server response body as the reason of the FetchError which
    prevents users of cozy-client from reacting appropriately when
    receiving such an error to their request.
    Therefore we homogenize our FetchError instances by always using the
    server response body to build the error reason.

    We need to add a new throwFetchErrors option to
    CozyStackClient.fetch to determine when to throw the error rather
    than emitting it as JSON requests expect the error to be thrown but we
    can't keep reading the response body from the JSON request method to
    build a new error to throw as it's already been read to build the
    emitted error.
    Besides, by doing so, we build the error only once, making sure we get
    the same kind no matter what type of request we make.

v54.0.1

12 Feb 16:25
Compare
Choose a tag to compare

54.0.1 (2025-02-12)

Bug Fixes

  • Allow disabling file name sanitization (7b33a66)

v54.0.0

11 Feb 13:07
Compare
Choose a tag to compare

54.0.0 (2025-02-11)

Bug Fixes

BREAKING CHANGES

  • The data-cozy-token injection is no longer supported
    for refreshToken.

We used to rely on DOMParser to extract the new token during a
refreshToken procedure. However, DOMParser is a web API, which is not
available in web workers, nor in node env. Therefore, we implement our
own HTML parsing, relying on the data-cozy attribute in HTML. We tried
using external libraries such as JSDom, fauxdom or linkedom, but got
build issues with all those libs. It was somehow manageable, but
required some additional config in consuming apps. As the HTML parsing
is quite basic, we decided that it is not worth the effort, and we now
do the parsing ourselves, making it available in web, workers, and node
envs.

As a consequence, we do not support the data-cozy-token existence
anymore, as it would require extra work and is seen as deprecated for
several years now. If your app still somehow require it, you need to
migrate the app template to rely on data-cozy like this: https://github.com/cozy/cozy-drive/blob/master/src/targets/browser/index.ejs#L37

v53.2.1

05 Feb 08:28
Compare
Choose a tag to compare

53.2.1 (2025-02-05)

Bug Fixes

  • deps: Upgrade cozy-pouch-link's parcel (4773f13)

v53.2.0

03 Feb 09:07
Compare
Choose a tag to compare

53.2.0 (2025-02-03)

Features

  • Add OAuth client last synced datetime update (0dcd553)