Magickbase / nervos-official-website

nervos.org
https://nervos-official-website.vercel.app/
3 stars 16 forks source link

fix(deps): update dependency @tanstack/react-query to v4.29.17 #204

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@tanstack/react-query (source) 4.29.14 -> 4.29.17 age adoption passing confidence

Release Notes

tanstack/query (@​tanstack/react-query) ### [`v4.29.17`](https://togithub.com/TanStack/query/releases/tag/v4.29.17) [Compare Source](https://togithub.com/tanstack/query/compare/v4.29.16...v4.29.17) Version 4.29.17 - 6/25/2023, 2:33 PM #### Changes ##### Refactor - query: add more context to "Missing queryFn" error ([#​5620](https://togithub.com/tanstack/query/issues/5620)) ([`9077bb9`](https://togithub.com/tanstack/query/commit/9077bb96)) by GLabat #### Packages - [@​tanstack/query-core](https://togithub.com/tanstack/query-core)[@​4](https://togithub.com/4).29.17 - [@​tanstack/query-persist-client-core](https://togithub.com/tanstack/query-persist-client-core)[@​4](https://togithub.com/4).29.17 - [@​tanstack/query-async-storage-persister](https://togithub.com/tanstack/query-async-storage-persister)[@​4](https://togithub.com/4).29.17 - [@​tanstack/query-broadcast-client-experimental](https://togithub.com/tanstack/query-broadcast-client-experimental)[@​4](https://togithub.com/4).29.17 - [@​tanstack/query-sync-storage-persister](https://togithub.com/tanstack/query-sync-storage-persister)[@​4](https://togithub.com/4).29.17 - [@​tanstack/react-query](https://togithub.com/tanstack/react-query)[@​4](https://togithub.com/4).29.17 - [@​tanstack/react-query-devtools](https://togithub.com/tanstack/react-query-devtools)[@​4](https://togithub.com/4).29.17 - [@​tanstack/react-query-persist-client](https://togithub.com/tanstack/react-query-persist-client)[@​4](https://togithub.com/4).29.17 - [@​tanstack/solid-query](https://togithub.com/tanstack/solid-query)[@​4](https://togithub.com/4).29.17 - [@​tanstack/svelte-query](https://togithub.com/tanstack/svelte-query)[@​4](https://togithub.com/4).29.17 - [@​tanstack/vue-query](https://togithub.com/tanstack/vue-query)[@​4](https://togithub.com/4).29.17 ### [`v4.29.16`](https://togithub.com/TanStack/query/releases/tag/v4.29.16) [Compare Source](https://togithub.com/tanstack/query/compare/v4.29.15...v4.29.16) Version 4.29.16 - 6/25/2023, 2:21 PM #### Changes ##### Refactor - rect-query: prefer client-only import over "use client" ([#​5626](https://togithub.com/tanstack/query/issues/5626)) ([`3e25f51`](https://togithub.com/tanstack/query/commit/3e25f51d)) by Dominik Dorfmeister #### Packages - [@​tanstack/react-query](https://togithub.com/tanstack/react-query)[@​4](https://togithub.com/4).29.16 - [@​tanstack/react-query-persist-client](https://togithub.com/tanstack/react-query-persist-client)[@​4](https://togithub.com/4).29.16 - [@​tanstack/react-query-devtools](https://togithub.com/tanstack/react-query-devtools)[@​4](https://togithub.com/4).29.16 ### [`v4.29.15`](https://togithub.com/TanStack/query/releases/tag/v4.29.15) [Compare Source](https://togithub.com/tanstack/query/compare/v4.29.14...v4.29.15) Version 4.29.15 - 6/20/2023, 4:52 PM #### Changes ##### Refactor - types: export query-cache related types ([#​5614](https://togithub.com/tanstack/query/issues/5614)) ([`c2d07d4`](https://togithub.com/tanstack/query/commit/c2d07d49)) by [@​indrajitbnikam](https://togithub.com/indrajitbnikam) ##### Docs - useMutation: fix incorrect `mutationKey` types ([#​5602](https://togithub.com/tanstack/query/issues/5602)) ([`28a96c7`](https://togithub.com/tanstack/query/commit/28a96c77)) by [@​CertainlyAria](https://togithub.com/CertainlyAria) - examples: Update useAppState in react-native example ([#​5557](https://togithub.com/tanstack/query/issues/5557)) ([`ab8dd55`](https://togithub.com/tanstack/query/commit/ab8dd555)) by Rudra Kishore G #### Packages - [@​tanstack/query-core](https://togithub.com/tanstack/query-core)[@​4](https://togithub.com/4).29.15 - [@​tanstack/query-persist-client-core](https://togithub.com/tanstack/query-persist-client-core)[@​4](https://togithub.com/4).29.15 - [@​tanstack/query-async-storage-persister](https://togithub.com/tanstack/query-async-storage-persister)[@​4](https://togithub.com/4).29.15 - [@​tanstack/query-broadcast-client-experimental](https://togithub.com/tanstack/query-broadcast-client-experimental)[@​4](https://togithub.com/4).29.15 - [@​tanstack/query-sync-storage-persister](https://togithub.com/tanstack/query-sync-storage-persister)[@​4](https://togithub.com/4).29.15 - [@​tanstack/react-query](https://togithub.com/tanstack/react-query)[@​4](https://togithub.com/4).29.15 - [@​tanstack/react-query-devtools](https://togithub.com/tanstack/react-query-devtools)[@​4](https://togithub.com/4).29.15 - [@​tanstack/react-query-persist-client](https://togithub.com/tanstack/react-query-persist-client)[@​4](https://togithub.com/4).29.15 - [@​tanstack/solid-query](https://togithub.com/tanstack/solid-query)[@​4](https://togithub.com/4).29.15 - [@​tanstack/svelte-query](https://togithub.com/tanstack/svelte-query)[@​4](https://togithub.com/4).29.15 - [@​tanstack/vue-query](https://togithub.com/tanstack/vue-query)[@​4](https://togithub.com/4).29.15

Configuration

πŸ“… Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log here.

vercel[bot] commented 1 year ago

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Comments Updated (UTC)
nervos-official-website βœ… Ready (Inspect) Visit Preview πŸ’¬ Add feedback Jun 25, 2023 4:06pm
pull-request-quantifier-deprecated[bot] commented 1 year ago

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

``` Label : No Changes Size : +0 -0 Percentile : 0% Total files changed: 1 Change summary by file extension: .lock : +0 -0 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.


Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

pull-request-quantifier-deprecated[bot] commented 1 year ago

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

``` Label : No Changes Size : +0 -0 Percentile : 0% Total files changed: 1 Change summary by file extension: .lock : +0 -0 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.


Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.