merge dev to main (v3.8.3)

[ymc9]

Summary by CodeRabbit

• New Features

  • Exposed a new query-key helper across the TanStack Query integrations, including React, Svelte, and Vue.

• Bug Fixes

  • Improved resilience when reading optional query settings, avoiding a potential runtime error when those settings are missing.

• Chores

  • Bumped the package version to 3.8.3 across the monorepo, including libraries, CLI, SDK, server, plugins, samples, and test packages.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR bumps the package version from 3.8.2 to 3.8.3 across all workspace manifests (root, packages, samples, tests). Additionally, tanstack-query's client.ts guards optimisticUpdate access with optional chaining, and react.ts, vue.ts, and svelte/index.svelte.ts add re-exports of getQueryKey.

Changes

Version Bump

Layer / File(s)	Summary
Bump version across manifests package.json, packages/**/package.json, samples/**/package.json, tests/**/package.json	The version field is updated from 3.8.2 to 3.8.3 in every package.json manifest across the monorepo.

Tanstack Query Fixes

Layer / File(s)	Summary
Optimistic update guard and getQueryKey re-export packages/clients/tanstack-query/src/common/client.ts, packages/clients/tanstack-query/src/react.ts, packages/clients/tanstack-query/src/vue.ts, packages/clients/tanstack-query/src/svelte/index.svelte.ts	getAllQueries now uses optional chaining (parsed.flags?.optimisticUpdate) to avoid crashes when flags is undefined, and getQueryKey is re-exported as public API from react, vue, and svelte entry points.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• zenstackhq/zenstack#2748: Overlaps directly with the tanstack-query changes in this PR, including the getQueryKey re-exports and the optimisticUpdate optional chaining fix in common/client.ts.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is a real summary of the release merge and version bump, and it is related to the changeset even though it omits the new export change.
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.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev

---

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.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

package.json (1)

5-17: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Pin packageManager to pnpm@10.12.1. package.json:17 still points at pnpm@10.33.0, which conflicts with the repo's {package.json,.npmrc} pnpm pinning rule and can make installs/CI use a different toolchain.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` around lines 5 - 17, The packageManager field in package.json
is still pinned to the wrong pnpm version; update it from pnpm@10.33.0 to
pnpm@10.12.1 so it matches the repository’s pnpm toolchain pinning. Make this
change directly in package.json and keep the existing packageManager setting
aligned with the repo’s pnpm versioning rule.

Source: Coding guidelines

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@package.json`:
- Around line 5-17: The packageManager field in package.json is still pinned to
the wrong pnpm version; update it from pnpm@10.33.0 to pnpm@10.12.1 so it
matches the repository’s pnpm toolchain pinning. Make this change directly in
package.json and keep the existing packageManager setting aligned with the
repo’s pnpm versioning rule.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 74e5259e-b1a2-4354-81a3-9a7d4976cb3d

📥 Commits

Reviewing files that changed from the base of the PR and between 29fbb97 and ad4ea73.

📒 Files selected for processing (32)

• package.json
• packages/auth-adapters/better-auth/package.json
• packages/cli/package.json
• packages/clients/client-helpers/package.json
• packages/clients/fetch-client/package.json
• packages/clients/tanstack-query/package.json
• packages/clients/tanstack-query/src/common/client.ts
• packages/clients/tanstack-query/src/react.ts
• packages/clients/tanstack-query/src/svelte/index.svelte.ts
• packages/clients/tanstack-query/src/vue.ts
• packages/common-helpers/package.json
• packages/config/eslint-config/package.json
• packages/config/tsdown-config/package.json
• packages/config/typescript-config/package.json
• packages/config/vitest-config/package.json
• packages/create-zenstack/package.json
• packages/ide/vscode/package.json
• packages/language/package.json
• packages/orm/package.json
• packages/plugins/policy/package.json
• packages/plugins/soft-delete/package.json
• packages/schema/package.json
• packages/sdk/package.json
• packages/server/package.json
• packages/testtools/package.json
• packages/zod/package.json
• samples/orm/package.json
• samples/taskforge/package.json
• tests/e2e/package.json
• tests/regression/package.json
• tests/runtimes/bun/package.json
• tests/runtimes/edge-runtime/package.json