-
Notifications
You must be signed in to change notification settings - Fork 1
fix(deps): update dependency cozy-client to v60 #83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-cozy-client-packages
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cf90162
to
8ab8095
Compare
4c2b935
to
0ff2cf4
Compare
d716f4a
to
500c44f
Compare
500c44f
to
cc3b7b0
Compare
c19d519
to
cabae33
Compare
cabae33
to
10b4e97
Compare
10b4e97
to
aebd39a
Compare
9676ed9
to
824ba74
Compare
824ba74
to
a1dc58f
Compare
2eeb3db
to
b043af7
Compare
a4a418c
to
97d767d
Compare
97d767d
to
e1f8dfa
Compare
eb82fb8
to
b1913d5
Compare
a1c1008
to
e809fab
Compare
0e9a2b9
to
06d89e1
Compare
db84b41
to
5988442
Compare
b3da271
to
7bd65eb
Compare
0d30a6a
to
2624ff1
Compare
7e23815
to
e6b7c60
Compare
e6b7c60
to
51ceb84
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^40.3.0
->^60.13.0
Release Notes
cozy/cozy-client (cozy-client)
v60.13.0
Compare Source
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
v60.12.3
Compare Source
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
v60.12.2
Compare Source
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
v60.12.1
Compare Source
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
v60.12.0
Compare Source
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
v60.11.0
Compare Source
Features
60.10.1 (2025-10-03)
Bug Fixes
v60.9.0
Compare Source
Features
v60.8.0
Compare Source
Features
v60.7.0
Compare Source
Features
v60.6.0
Compare Source
Bug Fixes
Features
60.5.1 (2025-09-02)
Bug Fixes
v60.5.0
Compare Source
Bug Fixes
Features
60.5.1 (2025-09-02)
Bug Fixes
v60.3.0
Compare Source
Features
v60.2.0
Compare Source
Features
60.1.1 (2025-07-24)
Bug Fixes
v60.1.1
Compare Source
Features
60.1.1 (2025-07-24)
Bug Fixes
v60.1.0
Compare Source
Features
60.1.1 (2025-07-24)
Bug Fixes
v60.0.0
Compare Source
Bug Fixes
Features
makeNewDocument
API method (678c1dd)BREAKING CHANGES
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
oncozy-client options to ease migration, e.g:
However, please not this has performance impact, as it forces
extra-check on store queries evaluation.
client.makeNewDocument
no longer exists, pleaseremove 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
shared_docs
parameter (24a2825)v59.3.0
Compare Source
Features
v59.2.0
Compare Source
Features
59.1.1 (2025-07-01)
Bug Fixes
v59.1.1
Compare Source
Features
59.1.1 (2025-07-01)
Bug Fixes
v59.1.0
Compare Source
Features
59.1.1 (2025-07-01)
Bug Fixes
v59.0.0
Compare Source
Bug Fixes
BREAKING CHANGES
of handling the
data
attribute at the root of the response.For example:
v58.5.0
Compare Source
Features
v58.4.0
Compare Source
Bug Fixes
Features
58.3.1 (2025-06-11)
Note: Version bump only for package cozy-client
v58.3.1
Compare Source
Bug Fixes
Features
58.3.1 (2025-06-11)
Note: Version bump only for package cozy-client
v58.3.0
Compare Source
Bug Fixes
Features
58.3.1 (2025-06-11)
Note: Version bump only for package cozy-client
v58.2.0
Compare Source
Bug Fixes
Features
v58.1.0
Compare Source
Features
58.0.1 (2025-05-14)
Bug Fixes
v58.0.1
Compare Source
Features
58.0.1 (2025-05-14)
Bug Fixes
v58.0.0
Compare Source
Features
58.0.1 (2025-05-14)
Bug Fixes
v57.7.2
Compare Source
Features
useCustomStore
rather thanstore
(eccc81e)BREAKING CHANGES
the boolean
store
option. The naming is confusing, because we couldinterpret 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 theintention.
If your application was using
store: false
in the cozy-clientinstanciation, you should now use
useCustomStore: true
.57.7.2 (2025-05-05)
Bug Fixes
57.7.1 (2025-04-24)
Bug Fixes
v57.7.1
Compare Source
Features
useCustomStore
rather thanstore
(eccc81e)BREAKING CHANGES
the boolean
store
option. The naming is confusing, because we couldinterpret 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 theintention.
If your application was using
store: false
in the cozy-clientinstanciation, you should now use
useCustomStore: true
.57.7.2 (2025-05-05)
Bug Fixes
57.7.1 (2025-04-24)
Bug Fixes
v57.7.0
Compare Source
Features
useCustomStore
rather thanstore
(eccc81e)BREAKING CHANGES
the boolean
store
option. The naming is confusing, because we couldinterpret 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 theintention.
If your application was using
store: false
in the cozy-clientinstanciation, you should now use
useCustomStore: true
.57.7.2 (2025-05-05)
Bug Fixes
57.7.1 (2025-04-24)
Bug Fixes
v57.6.0
Compare Source
Features
57.6.1 (2025-04-03)
Bug Fixes
cozyPouchData
for sqlite (8427309)v57.5.0
Compare Source
Features
v57.4.0
Compare Source
Features
v57.3.0
Compare Source
Bug Fixes
Features
v57.2.0
Compare Source
Features
v57.1.0
Compare Source
Features
v57.0.0
Compare Source
Features
BREAKING CHANGES
SharingCollection.create method.
v56.0.0
Compare Source
Features
BREAKING CHANGES
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
Features
BREAKING CHANGES
The
reason
attribute of non-JSON fetch errors is nolonger a string composed of the server response status and status
text.
We used to have 2 different kinds of values for the
reason
attributeof
FetchError
built inCozyStackClient
:(which may contain details about what when wrong, especially for 400
status responses) for JSON requests
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
whichprevents users of
cozy-client
from reacting appropriately whenreceiving such an error to their request.
Therefore we homogenize our
FetchError
instances by always using theserver response body to build the error
reason
.We need to add a new
throwFetchErrors
option toCozyStackClient.fetch
to determine when to throw the error ratherthan 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
v54.0.1
Compare Source
Bug Fixes
Features
BREAKING CHANGES
The
reason
attribute of non-JSON fetch errors is nolonger a string composed of the server response status and status
text.
We used to have 2 different kinds of values for the
reason
attributeof
FetchError
built inCozyStackClient
:(which may contain details about what when wrong, especially for 400
status responses) for JSON requests
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
whichprevents users of
cozy-client
from reacting appropriately whenreceiving such an error to their request.
Therefore we homogenize our
FetchError
instances by always using theserver response body to build the error
reason
.We need to add a new
throwFetchErrors
option toCozyStackClient.fetch
to determine when to throw the error ratherthan 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
v54.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
The
reason
attribute of non-JSON fetch errors is nolonger a string composed of the server response status and status
text.
We used to have 2 different kinds of values for the
reason
attributeof
FetchError
built inCozyStackClient
:(which may contain details about what when wrong, especially for 400
status responses) for JSON requests
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
whichprevents users of
cozy-client
from reacting appropriately whenreceiving such an error to their request.
Therefore we homogenize our
FetchError
instances by always using theserver response body to build the error
reason
.We need to add a new
throwFetchErrors
option toCozyStackClient.fetch
to determine when to throw the error ratherthan 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
v53.2.0
Compare Source
Bug Fixes
BREAKING CHANGES
data-cozy-token
injection is no longer supportedfor 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 triedusing 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
existenceanymore, 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
v53.1.1
Compare Source
Features
53.1.1 (2025-01-29)
Bug Fixes
v53.1.0
Compare Source
Features
53.1.1 (2025-01-29)
Bug Fixes
v53.0.0
Compare Source
Features
BREAKING CHANGES
This function creates or updates a share link.
via
createSharingLink
is no longeremail
butcode
.You can either adapt your code accordingly or
simply add the option
{ codes: 'email' }
when callingcreateSharingLink
.v52.2.0
Compare Source
Features
shortcut
option to getDiscoveryLink (1d45ab2), closes cozy/cozy-stack#450352.1.1 (2025-01-15)
Bug Fixes
v52.1.1
Compare Source
Features
shortcut
option to getDiscoveryLink (1d45ab2), closes cozy/cozy-stack#450352.1.1 (2025-01-15)
Bug Fixes
v52.1.0
Compare Source
Features
shortcut
option to getDiscoveryLink (1d45ab2), closes cozy/cozy-stack#450352.1.1 (2025-01-15)
Bug Fixes
v52.0.1
Compare Source
Features
52.0.1 (2025-01-06)
Bug Fixes
v52.0.0
Compare Source
Features
52.0.1 (2025-01-06)
Bug Fixes
v51.7.0
Compare Source
Features
51.6.1 (2024-12-16)
Note: Version bump only for package cozy-client
v51.6.1
Compare Source
Features
51.6.1 (2024-12-16)
Note: Version bump only for package cozy-client
v51.6.0
Compare Source
Features
51.6.1 (2024-12-16)
Note: Version bump only for package cozy-client
v51.5.0
Compare Source
Bug Fixes
Features
v51.4.0
Compare Source
Features
loadInstanceOptionsFromStacks
queries (55dd291)51.3.1 (2024-11-28)
Note: Version bump only for package cozy-client
v51.3.1
Compare Source
Features
loadInstanceOptionsFromStacks
queries (55dd291)51.3.1 (2024-11-28)
Note: Version bump only for package cozy-client
v51.3.0
Compare Source
Features
loadInstanceOptionsFromStacks
queries (55dd291)51.3.1 (2024-11-28)
Note: Version bump only for package cozy-client
v51.2.0
Compare Source
Features
v51.1.0
Compare Source
Features
51.0.1 (2024-11-15)
Bug Fixes
v51.0.1
Compare Source
Features
51.0.1 (2024-11-15)
Bug Fixes
v51.0.0
Compare Source
Features
51.0.1 (2024-11-15)
Bug Fixes
v50.4.0
Compare Source
Features
io.cozy.files
).getByIds (8463cc4)50.3.1 (2024-11-06)
Bug Fixes
limitBy()
limit argument in DSL (658ec8c)v50.3.1
Compare Source
Features
io.cozy.files
).getByIds (8463cc4)50.3.1 (2024-11-06)
Bug Fixes
limitBy()
limiConfiguration
📅 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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.