chore: Bump up react query 5.59.15

[memoyil]

---

PR-Codex overview

This PR updates the version of @tanstack/react-query across multiple packages to 5.59.15 from 5.52.1, ensuring consistency and compatibility with the latest features and fixes.

Detailed summary

• Updated @tanstack/react-query from ^5.52.1 to 5.59.15 in:
  • packages/wagmi/package.json
  • apps/blog/package.json
  • apps/games/package.json
  • apps/web/package.json
  • packages/awgmi/package.json
  • apps/gamification/package.json
  • apps/aptos/package.json
• Adjusted version references in pnpm-lock.yaml to reflect the new version.
• Updated dependency versions in various package snapshots to match the new @tanstack/react-query version.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4df6415

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
aptos-web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 19, 2024 6:29pm
blog	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 19, 2024 6:29pm
bridge	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 19, 2024 6:29pm
games	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 19, 2024 6:29pm
gamification	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 19, 2024 6:29pm
web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 19, 2024 6:29pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
uikit	⬜️ Ignored (Inspect)	Visit Preview		Oct 19, 2024 6:29pm

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/deepmerge@4.3.1	None	0	31.2 kB	tehshrike

🚮 Removed packages: npm/@storybook/addon-a11y@7.5.3, npm/@storybook/addon-actions@7.5.3, npm/@storybook/addon-essentials@7.5.3, npm/@storybook/addon-links@7.5.3, npm/@storybook/builder-vite@7.5.3

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	CI
Filesystem access	npm/source-map-support@0.5.21	Module: fs Location: Package overview	🚫
Filesystem access	npm/readdirp@3.6.0	Module: fs Location: Package overview	🚫
Filesystem access	npm/esbuild@0.17.19	Module: fs Location: Package overview	🚫
Environment variable access	npm/esbuild@0.17.19	Env Vars: ESBUILD_BINARY_PATH Location: Package overview	🚫
Environment variable access	npm/esbuild@0.17.19	Location: Package overview	🚫
Environment variable access	npm/esbuild@0.17.19	Env Vars: ESBUILD_WORKER_THREADS Location: Package overview	🚫
Environment variable access	npm/esbuild@0.17.19	Env Vars: ESBUILD_MAX_BUFFER Location: Package overview	🚫
Deprecated	npm/sourcemap-codec@1.4.8	Reason: Please use @jridgewell/sourcemap-codec instead	🚫
Deprecated	npm/rollup-plugin-inject@3.0.2	Reason: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-inject.	🚫
Environment variable access	npm/rollup-plugin-node-polyfills@0.2.1	Env Vars: READABLE_STREAM Location: Package overview	🚫
Environment variable access	npm/rollup-plugin-node-polyfills@0.2.1	Env Vars: READABLE_STREAM Location: Package overview	🚫
Environment variable access	npm/rollup-plugin-node-polyfills@0.2.1	Env Vars: NODE_DEBUG Location: Package overview	🚫
Filesystem access	npm/blake3-wasm@2.1.5	Module: fs Location: Package overview	🚫
Filesystem access	npm/hardhat@2.22.2	Module: fs-extra Location: Package overview	🚫
Filesystem access	npm/hardhat@2.22.2	Module: fs/promises Location: Package overview	🚫
Filesystem access	npm/hardhat@2.22.2	Module: fs Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: http_proxy Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: DO_NOT_SET_THIS_ENV_VAR____IS_HARDHAT_CI Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: TS_NODE_PROJECT Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: TS_NODE_FILES Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: key Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: HARDHAT_ENABLE_SENTRY Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: GITHUB_ACTIONS Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: DISPLAY Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: WAYLAND_DISPLAY Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: NOW Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: DEPLOYMENT_ID Location: Package overview	🚫
Environment variable access	npm/hardhat@2.22.2	Env Vars: CODEBUILD_BUILD_NUMBER Location: Package overview	🚫

View full report↗︎

Next steps

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/source-map-support@0.5.21
• @SocketSecurity ignore npm/readdirp@3.6.0
• @SocketSecurity ignore npm/esbuild@0.17.19
• @SocketSecurity ignore npm/sourcemap-codec@1.4.8
• @SocketSecurity ignore npm/rollup-plugin-inject@3.0.2
• @SocketSecurity ignore npm/rollup-plugin-node-polyfills@0.2.1
• @SocketSecurity ignore npm/blake3-wasm@2.1.5
• @SocketSecurity ignore npm/hardhat@2.22.2