Skip to content

chore(deps): update dependency @tanstack/react-query to v4.40.1 #57

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

Merged
merged 1 commit into from
Jul 28, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 28, 2025

This PR contains the following updates:

Package Change Age Confidence
@tanstack/react-query (source) 4.36.1 -> 4.40.1 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

TanStack/query (@​tanstack/react-query)

v4.40.1

Compare Source

Version 4.40.1 - 7/4/25, 1:18 PM

Changes

Fix
Docs

Packages

v4.40.0

Compare Source

Version 4.40.0 - 6/17/25, 4:44 PM

Changes

Feat
  • query-core, react-query: backport v5 types, deprecate isLoading in favor of isPending in mutation observer results (#​9266) (693a471) by @​manudeli

Packages

v4.39.2

Compare Source

Version 4.39.2 - 6/9/25, 9:36 AM

Changes

Fix

Packages

v4.39.1

Compare Source

Version 4.39.1 - 5/31/25, 1:09 PM (Manual Release)

Changes

Fix
  • v4: ensure packages are built during CI (#​9227) (4f93b86) by Lachlan Collins
Ci
  • v4: fix Nx commands (52f93a5) by Lachlan Collins

Packages

v4.39.0

Compare Source

Version 4.39.0 - 5/31/25, 1:07 AM

Changes

Feat
Chore
  • Fix incorrect npm tag for previous version release (v4) (#​6659) (ce313af) by Lachlan Collins
Ci
Docs
Other

Packages


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 this update again.


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

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

Copy link
Contributor Author

renovate bot commented Jul 28, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @openedx/[email protected]
npm error Found: @types/[email protected]
npm error node_modules/@types/react
npm error   peerOptional @types/react@"^16.8 || ^17.0 || ^18.0" from [email protected]
npm error   node_modules/@openedx/frontend-plugin-framework/node_modules/react-redux
npm error     react-redux@"8.1.1" from @openedx/[email protected]
npm error     node_modules/@openedx/frontend-plugin-framework
npm error       peer @openedx/frontend-plugin-framework@"^1.7.0" from the root project
npm error   peerOptional @types/react@"^18.0.0 || ^19.0.0" from @testing-library/[email protected]
npm error   node_modules/@testing-library/react
npm error     dev @testing-library/react@"^16.0.0" from the root project
npm error   13 more (@types/hoist-non-react-statics, @types/react-redux, ...)
npm error
npm error Could not resolve dependency:
npm error peer @tanstack/react-query@"4.40.1" from the root project
npm error
npm error Conflicting peer dependency: @types/[email protected]
npm error node_modules/@types/react
npm error   peerOptional @types/react@"^19.1.0" from [email protected]
npm error   node_modules/react-native
npm error     peerOptional react-native@"*" from @tanstack/[email protected]
npm error     node_modules/@tanstack/react-query
npm error       peer @tanstack/react-query@"4.40.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-07-28T13_38_47_875Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-07-28T13_38_47_875Z-debug-0.log

@renovate renovate bot enabled auto-merge (squash) July 28, 2025 13:38
@renovate renovate bot merged commit 1677103 into main Jul 28, 2025
3 of 5 checks passed
@renovate renovate bot deleted the renovate/tanstack-query-monorepo branch July 28, 2025 13:39
@tecoholic
Copy link
Contributor

@farhaanbukhsh @bmtcril Hi, I noticed that the CI failed on the README update PR. Seems to have been caused by updated of @tanstack/react-query from 4.36.1 to 4.40.0.

The CI clearly failed in this PR, however, renovate Bot has merged the change. I am not familiat with RenovateBot. But I would assume the auto-merge would happen only when CI checks pass. Can you kindly take a look?

@saraburns1
Copy link
Contributor

@farhaanbukhsh @bmtcril Hi, I noticed that the CI failed on the README update PR. Seems to have been caused by updated of @tanstack/react-query from 4.36.1 to 4.40.0.

The CI clearly failed in this PR, however, renovate Bot has merged the change. I am not familiat with RenovateBot. But I would assume the auto-merge would happen only when CI checks pass. Can you kindly take a look?

I'll see if I can figure this out

@saraburns1
Copy link
Contributor

@tecoholic can you approve & merge this? should fix the CI #58

@farhaanbukhsh
Copy link
Member

@saraburns1 thank you so much for the PR, I have merged it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants