fix(deps): update dependency cozy-client to v60 #1027

the relationship hydration is made only if the
relationship exists in the document, so the developer should not assume
a document.relationshipName is always defined, anymore.
As an alternative, it is possible to pass autoHydrate on
cozy-client options to ease migration, e.g:

const newClient = new CozyClient({
  schema,
  autoHydrate: true
})

However, please not this has performance impact, as it forces
extra-check on store queries evaluation.

client.makeNewDocument no longer exists, please
remove any code using it.

This method was not very useful and was relying on the full hydratation
of the schema relationships. This behaviour should be changed
eventually.

`v59.4.0`

Compare Source

Features

Add shared_docs parameter (24a2825)

`v59.3.0`

Compare Source

Features

Add a method to fetch shared drives (04d18b4)

`v59.2.0`

Compare Source

Features

Add helper for debug flag (737bbc4)

59.1.1 (2025-07-01)

Bug Fixes

Filter missing documents from store (180af2c)

`v59.1.1`

Compare Source

Features

Add helper for debug flag (737bbc4)

59.1.1 (2025-07-01)

Bug Fixes

Filter missing documents from store (180af2c)

`v59.1.0`

Compare Source

Features

Add helper for debug flag (737bbc4)

59.1.1 (2025-07-01)

Bug Fixes

Filter missing documents from store (180af2c)

`v59.0.0`

Compare Source

Bug Fixes

Normalize data for trash-related methods (754c45c)

BREAKING CHANGES

if you were relying on deleteFilePermanently, take care
of handling the data attribute at the root of the response.
For example:

const result = fileCollection.deleteFilePermanently() // old
const { data: result } = fileCollection.deleteFilePermanently() // new

`v58.5.0`

Compare Source

Features

Add doctypes model and fetch function (f115786)

`v58.4.0`

Compare Source

Bug Fixes

Do not throw when file content is defined but empty (1d0e99e)

Features

Add Docs helper (4bb5e23)

58.3.1 (2025-06-11)

Note: Version bump only for package cozy-client

`v58.3.1`

Compare Source

Bug Fixes

Do not throw when file content is defined but empty (1d0e99e)

Features

Add Docs helper (4bb5e23)

58.3.1 (2025-06-11)

Note: Version bump only for package cozy-client

`v58.3.0`

Compare Source

Bug Fixes

Do not throw when file content is defined but empty (1d0e99e)

Features

Add Docs helper (4bb5e23)

58.3.1 (2025-06-11)

Note: Version bump only for package cozy-client

`v58.2.0`

Compare Source

Bug Fixes

Correctly handle missing doc on PouchDB (4aa7e75)
Do not throw if there is no database for a doctype (6b73ca9)
Do not throw when doc has relationship but not schema (be7da5a)
Exclude design docs from response (c092b4e)

Features

Add readOnly option (f84d8db)
Handle paths locally (18049bc)

`v58.1.0`

Compare Source

Features

Add DataProxyLink (44d4d07)

58.0.1 (2025-05-14)

Bug Fixes

Downgrade react-native 0.65.x to 0.63.x (ecfd141)

`v58.0.1`

Compare Source

Features

Add DataProxyLink (44d4d07)

58.0.1 (2025-05-14)

Bug Fixes

Downgrade react-native 0.65.x to 0.63.x (ecfd141)

`v58.0.0`

Compare Source

Features

Add DataProxyLink (44d4d07)

58.0.1 (2025-05-14)

Bug Fixes

Downgrade react-native 0.65.x to 0.63.x (ecfd141)

`v57.7.2`

Compare Source

Features

Add disableStoreForQueries options to bypass store (8ab649c)
Use useCustomStore rather than store (eccc81e)

BREAKING CHANGES

to pass a custom store from the app, we used to rely on
the boolean store option. The naming is confusing, because we could
interpret it as completely disabling the redux store, which is not the
case, as the aim is to use either the cozy-client internal store, or the
application own store. It was also confusing in the code, as the store
variable is the store itself.
Thus, we rename the option in useCustomStore to better reflect the
intention.

If your application was using store: false in the cozy-client
instanciation, you should now use useCustomStore: true.

57.7.2 (2025-05-05)

Bug Fixes

Add missing permissions translations (21ade3d)

57.7.1 (2025-04-24)

Bug Fixes

Ignore Twake prefix in getAppDisplayName (22e785c)

`v57.7.1`

Compare Source

Features

Add disableStoreForQueries options to bypass store (8ab649c)
Use useCustomStore rather than store (eccc81e)

BREAKING CHANGES

to pass a custom store from the app, we used to rely on
the boolean store option. The naming is confusing, because we could
interpret it as completely disabling the redux store, which is not the
case, as the aim is to use either the cozy-client internal store, or the
application own store. It was also confusing in the code, as the store
variable is the store itself.
Thus, we rename the option in useCustomStore to better reflect the
intention.

If your application was using store: false in the cozy-client
instanciation, you should now use useCustomStore: true.

57.7.2 (2025-05-05)

Bug Fixes

Add missing permissions translations (21ade3d)

57.7.1 (2025-04-24)

Bug Fixes

Ignore Twake prefix in getAppDisplayName (22e785c)

`v57.7.0`

Compare Source

Features

Add disableStoreForQueries options to bypass store (8ab649c)
Use useCustomStore rather than store (eccc81e)

BREAKING CHANGES

to pass a custom store from the app, we used to rely on
the boolean store option. The naming is confusing, because we could
interpret it as completely disabling the redux store, which is not the
case, as the aim is to use either the cozy-client internal store, or the
application own store. It was also confusing in the code, as the store
variable is the store itself.
Thus, we rename the option in useCustomStore to better reflect the
intention.

If your application was using store: false in the cozy-client
instanciation, you should now use useCustomStore: true.

57.7.2 (2025-05-05)

Bug Fixes

Add missing permissions translations (21ade3d)

57.7.1 (2025-04-24)

Bug Fixes

Ignore Twake prefix in getAppDisplayName (22e785c)

`v57.6.0`

Compare Source

Features

Add sortApplicationsList in apps model (eed4fad)
Use a shorter version of sortApplicationsList (ae7ae91)

57.6.1 (2025-04-03)

Bug Fixes

Add opsqlite as devDep (3656709)
Do not use transaction for read queries (e33547f)
Handle cozyPouchData for sqlite (8427309)
Move sqliteDb in a native code file (32881bf)
Pagination (619aa51)
PersistCozyData for new docs (baaca44)
SQL limit (3dc6ac8)

`v57.5.0`

Compare Source

Features

Migrate to Yarn 4 (3e08b74)
Update peer deps version (30369af)
Update ts config after Yarn 4 (db928e1)

`v57.4.0`

Compare Source

Features

Improve normalization performances (853b4a1)
Improve persistVirtualDocuments performances (884c4d9)

`v57.3.0`

Compare Source

Bug Fixes

Correctly handle document's store updates (96cef80)

Features

Improve merge performances (6573f3b)

`v57.2.0`

Compare Source

Features

Add ifMatch option to FileCollection methods (1e60e3c)

`v57.1.0`

Compare Source

Features

Improve store query performance for id queries (449c7cd)

`v57.0.0`

Compare Source

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`

Compare Source

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.0.0`

Compare Source

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.

54.0.1 (2025-02-12)

Bug Fixes

Allow disabling file name sanitization (7b33a66)

`v54.0.1`

Compare Source

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.

54.0.1 (2025-02-12)

Bug Fixes

Allow disabling file name sanitization (7b33a66)

`v54.0.0`

Compare Source

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.

54.0.1 (2025-02-12)

Bug Fixes

Allow disabling file name sanitization (7b33a66)

`v53.2.0`

Compare Source

Bug Fixes

Correctly handle replication refreshToken (38ef6aa)
Make refreshToken work in worker and node env (e392131), closes /github.com/cozy/cozy-drive/blob/master/src/targets/browser/index.ejs#L37

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:

53.2.1 (2025-02-05)

Bug Fixes

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

`v53.1.1`

Compare Source

Features

Add OAuth client last synced datetime update (0dcd553)

53.1.1 (2025-01-29)

Bug Fixes

Do not read pouch adapter name at login (b21118e)
Links' onLogin should be awaited (8a63504)

`v53.1.0`

Compare Source

Features

Add OAuth client last synced datetime update (0dcd553)

53.1.1 (2025-01-29)

Configuration

📅 Schedule: Branch creation - "on saturday" in timezone Europe/Paris, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot requested a review from a team as a code owner April 5, 2025 06:27

renovate bot added the dependencies Pull requests that update a dependency file label Apr 5, 2025

renovate bot force-pushed the renovate/major-cozy-client-packages branch from 4a42189 to b4fbb8b Compare April 11, 2025 23:12

renovate bot force-pushed the renovate/major-cozy-client-packages branch from b4fbb8b to 7feed60 Compare April 25, 2025 22:00

renovate bot force-pushed the renovate/major-cozy-client-packages branch from 7feed60 to 81e401a Compare May 9, 2025 22:05

renovate bot changed the title ~~fix(deps): update dependency cozy-client to v57~~ fix(deps): update dependency cozy-client to v58 May 9, 2025

renovate bot force-pushed the renovate/major-cozy-client-packages branch from 81e401a to a463379 Compare May 16, 2025 22:52

renovate bot force-pushed the renovate/major-cozy-client-packages branch from a463379 to 624be82 Compare May 23, 2025 23:39

renovate bot force-pushed the renovate/major-cozy-client-packages branch from 624be82 to 9e79f85 Compare June 14, 2025 01:03

renovate bot force-pushed the renovate/major-cozy-client-packages branch from 9e79f85 to 3455024 Compare June 27, 2025 23:30

renovate bot changed the title ~~fix(deps): update dependency cozy-client to v58~~ fix(deps): update dependency cozy-client to v59 Jun 27, 2025

renovate bot force-pushed the renovate/major-cozy-client-packages branch from 3455024 to e1a1072 Compare July 5, 2025 01:57

renovate bot force-pushed the renovate/major-cozy-client-packages branch from e1a1072 to ff4fa51 Compare July 19, 2025 01:50

renovate bot changed the title ~~fix(deps): update dependency cozy-client to v59~~ fix(deps): update dependency cozy-client to v60 Jul 19, 2025

renovate bot force-pushed the renovate/major-cozy-client-packages branch from ff4fa51 to 914aec2 Compare July 25, 2025 22:08

renovate bot force-pushed the renovate/major-cozy-client-packages branch from 914aec2 to 1cccaba Compare August 22, 2025 23:29

renovate bot force-pushed the renovate/major-cozy-client-packages branch 2 times, most recently from 20edd3f to 53227f5 Compare September 27, 2025 00:37

renovate bot force-pushed the renovate/major-cozy-client-packages branch from 53227f5 to 8ed03eb Compare October 4, 2025 00:47

renovate bot force-pushed the renovate/major-cozy-client-packages branch from 8ed03eb to e8a889d Compare October 11, 2025 00:57

renovate bot force-pushed the renovate/major-cozy-client-packages branch 2 times, most recently from 9565401 to 68c5f9b Compare October 24, 2025 23:53

renovate bot force-pushed the renovate/major-cozy-client-packages branch from 68c5f9b to 0e1ee1c Compare October 31, 2025 23:54

renovate bot force-pushed the renovate/major-cozy-client-packages branch from 0e1ee1c to 9e55767 Compare November 8, 2025 01:33

renovate bot force-pushed the renovate/major-cozy-client-packages branch from 9e55767 to e317554 Compare November 22, 2025 01:30

fix(deps): update dependency cozy-client to v60

999c537

renovate bot force-pushed the renovate/major-cozy-client-packages branch from e317554 to 999c537 Compare December 6, 2025 02:56

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update dependency cozy-client to v60 #1027

fix(deps): update dependency cozy-client to v60 #1027

Uh oh!

renovate bot commented Apr 5, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

fix(deps): update dependency cozy-client to v60 #1027

Are you sure you want to change the base?

fix(deps): update dependency cozy-client to v60 #1027

Uh oh!

Conversation

renovate bot commented Apr 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Features

Features

Features

60.17.2 (2025-11-19)

Bug Fixes

60.17.1 (2025-11-19)

Bug Fixes

Features

60.17.2 (2025-11-19)

Bug Fixes

60.17.1 (2025-11-19)

Bug Fixes

Features

60.17.2 (2025-11-19)

Bug Fixes

60.17.1 (2025-11-19)

Bug Fixes

Features

60.16.1 (2025-10-27)

Bug Fixes

Bug Fixes

Features

60.15.2 (2025-10-21)

Bug Fixes

60.15.1 (2025-10-21)

Bug Fixes

Bug Fixes

Features

60.15.2 (2025-10-21)

Bug Fixes

60.15.1 (2025-10-21)

Bug Fixes

Bug Fixes

Features

60.15.2 (2025-10-21)

Bug Fixes

60.15.1 (2025-10-21)

Bug Fixes

Features

Bug Fixes

Features

60.12.3 (2025-10-07)

Bug Fixes

60.12.2 (2025-10-06)

Bug Fixes

60.12.1 (2025-10-06)

Bug Fixes

Bug Fixes

Features

60.12.3 (2025-10-07)

Bug Fixes

60.12.2 (2025-10-06)

Bug Fixes

60.12.1 (2025-10-06)

Bug Fixes

Bug Fixes

Features

60.12.3 (2025-10-07)

Bug Fixes

60.12.2 (2025-10-06)

Bug Fixes

60.12.1 (2025-10-06)

Bug Fixes

Bug Fixes

Features

60.12.3 (2025-10-07)

Bug Fixes

60.12.2 (2025-10-06)

Bug Fixes

60.12.1 (2025-10-06)

Bug Fixes

Bug Fixes

renovate bot commented Apr 5, 2025 •

edited

Loading