chore: add react-query next bugs metadata

[pesoszpesosz]

🎯 Changes

• Add the standard bugs.url metadata entry for @tanstack/react-query-next-experimental.
• Point package consumers to the canonical TanStack Query issue tracker.
• Keep repository, homepage, funding, exports, dependencies, and runtime code unchanged.

✅ Checklist

• I have followed the steps in the Contributing guide.
• I have tested this code locally with pnpm run test:pr.
  • Not applicable for this package-metadata-only change. I ran the focused validation commands below instead.

🚀 Release Impact

• This change affects published code, and I have generated a changeset.
  • Not applicable: this does not change runtime behavior, public APIs, docs, or generated output.
• This change is docs/CI/dev-only (no release).
  • Treated as no-release package metadata maintenance.

Validation

• node -e "const p=require('./packages/react-query-next-experimental/package.json'); if (p.name !== '@tanstack/react-query-next-experimental' || p.bugs?.url !== 'https://github.com/TanStack/query/issues') throw new Error(JSON.stringify({name:p.name, bugs:p.bugs})); console.log(JSON.stringify({name:p.name, version:p.version, repository:p.repository, homepage:p.homepage, bugs:p.bugs}))"
• git diff --check
• npm pack --dry-run --ignore-scripts --json from packages/react-query-next-experimental

The dry-run package includes the updated package.json and the existing src files.

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR adds a bugs field to the @tanstack/react-query-next-experimental package manifest, linking users to the GitHub issues page for bug reporting. This is a standard npm package metadata entry.

Changes

Package Metadata

Layer / File(s)	Summary
Bugs field in package manifest packages/react-query-next-experimental/package.json	Added top-level bugs field to the package manifest pointing to the GitHub repository issues URL.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A bug field springs up, so neat and small,
Pointing folks to issues, one and all!
Package manifest now shines complete,
With metadata's gentle, simple beat. ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a bugs metadata field to the react-query-next package manifest.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The pull request description follows the required template structure with all key sections completed and well-documented.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}