update code submodules

[ymc9]

Summary by CodeRabbit

• Chores
  • Updated internal submodule references across multiple components to latest versions. No user-facing changes or functional modifications included in this release.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
zenstack-new-site	Ready	Preview	Comment	Nov 18, 2025 6:26pm

[coderabbitai]

Walkthrough

This PR updates nine documentation-related submodule pointers to newer commits across the ZenStack project. Each submodule reference is updated to a different commit hash, with no functional code changes in the parent repository.

Changes

Cohort / File(s)	Summary
ORM Documentation Submodules code-repos/zenstackhq/v3-doc-orm, code-repos/zenstackhq/v3-doc-orm-computed-fields, code-repos/zenstackhq/v3-doc-orm-policy, code-repos/zenstackhq/v3-doc-orm-polymorphism, code-repos/zenstackhq/v3-doc-orm-typed-json, code-repos/zenstackhq/v3-doc-orm-validation	Submodule pointers updated to newer commits
Additional Documentation Submodules code-repos/zenstackhq/v3-doc-quick-start, code-repos/zenstackhq/v3-doc-server-adapter, code-repos/zenstackhq/v3-doc-tanstack-query	Submodule pointers updated to newer commits

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verification of commit hash changes across all submodule references
• Confirmation that no functional code modifications exist in the parent repository

Possibly related PRs

• doc: v3 query as a service #500: Updates to server-adapter documentation corresponding to the v3-doc-server-adapter submodule pointer change
• doc: v3 tanstack-query docs #502: Updates to TanStack Query documentation corresponding to the v3-doc-tanstack-query submodule pointer change

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'update code submodules' is directly related to the changeset, which consists entirely of submodule pointer updates across nine different repositories.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/update-submodules

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0449518 and 5a26f91.

📒 Files selected for processing (9)

• code-repos/zenstackhq/v3-doc-orm (1 hunks)
• code-repos/zenstackhq/v3-doc-orm-computed-fields (1 hunks)
• code-repos/zenstackhq/v3-doc-orm-policy (1 hunks)
• code-repos/zenstackhq/v3-doc-orm-polymorphism (1 hunks)
• code-repos/zenstackhq/v3-doc-orm-typed-json (1 hunks)
• code-repos/zenstackhq/v3-doc-orm-validation (1 hunks)
• code-repos/zenstackhq/v3-doc-quick-start (1 hunks)
• code-repos/zenstackhq/v3-doc-server-adapter (1 hunks)
• code-repos/zenstackhq/v3-doc-tanstack-query (1 hunks)

🔇 Additional comments (9)

code-repos/zenstackhq/v3-doc-orm-typed-json (1)

1-1: All submodule pointers are properly formatted and coordinated.

The verification confirms:

• All 9 submodule commit hashes have valid SHA-1 format (40 hex characters)
• The v3-doc-orm-typed-json update from 1237f4c to 78beb33 is part of a coordinated synchronization across documentation submodules
• All submodule references are properly registered in .gitmodules

Before merging, manually verify that the external repository commits exist and the changes are compatible with the parent documentation.

code-repos/zenstackhq/v3-doc-orm-policy (1)

1-1: Verify the submodule commit update is intentional.

Submodule pointer updated from ccbde6f... to 5d1ecc3.... Please confirm:

1. The new commit hash exists in the v3-doc-orm-policy repository
2. This is a forward-moving update with intended improvements (not a revert)
3. Any breaking changes or migration steps required are documented

Note: The AI summary mentions nine submodule updates, but only one file is provided for review. Ensure all submodule updates are captured.

code-repos/zenstackhq/v3-doc-tanstack-query (1)

1-1: Submodule commit is valid and verified.

Verification confirms that commit 52a9816e6eba1ba7d96e499b062c2c9f539a850d exists in the remote repository and is currently the HEAD on the main branch. All nine submodule updates follow a consistent pattern with valid commit hashes. No issues identified.

code-repos/zenstackhq/v3-doc-orm (1)

1-1: Verify the submodule commit exists and review the scope of changes.

Submodule pointer updates are straightforward, but it's important to confirm the new commit is valid and accessible in the remote repository. Additionally, understanding what changed in the updated ORM documentation submodule helps assess whether this aligns with the broader PR objectives.

Please confirm:

1. The commit hash ed333f6978625f201f2250075ec5ad74c06d9809 exists in the remote v3-doc-orm repository.
2. A summary of what changed between the old and new commits (feature additions, fixes, breaking changes, etc.).
3. Whether the other 8 submodule updates mentioned in the AI summary follow the same pattern and are aligned with this one.

code-repos/zenstackhq/v3-doc-orm-validation (1)

1-1: Submodule pointer update verified.

Commit 823addfc483da683dfaa41f7b452993df97dd406 exists in the v3-doc-orm-validation repository. The update is safe to merge.

code-repos/zenstackhq/v3-doc-orm-polymorphism (1)

1-1: Routine submodule pointer update.

The commit hash is being updated as part of a coordinated 9-submodule update across the PR. Since the provided context confirms this is maintenance-focused with no functional code changes in the parent repository, this change aligns with the PR objectives.

To ensure the integrity of this submodule update, please verify that:

• The new commit hash 19b16db342d1174d996fc1d4352bf712b36ffe0d exists in the zenstackhq/v3-doc-orm-polymorphism repository
• The update is from an expected branch and does not introduce breaking changes to the documentation

code-repos/zenstackhq/v3-doc-orm-computed-fields (1)

1-1: Submodule update is valid and safe to merge.

The commit e3e28ed50d26f069a6fbae2b3de94ad7bdf34492 exists in the target repository with message "update to latest zenstack". This is part of PR #2302 (chore: update to Prisma 6.19), a routine maintenance update that includes synchronizing documentation. Since the submodule references a documentation-only repository, there is no risk of breaking changes to functionality.

code-repos/zenstackhq/v3-doc-server-adapter (2)

1-1: Clarify the discrepancy between the enriched summary and the actual commit hash.

The enriched summary states the commit is being updated from fc438dc... to ed333f6..., but the annotated code shows the new commit as d4ad9aa4bc6889b9c49cb34d703c7f346ab48778. Please confirm which commit hash is correct and ensure consistency across all nine submodule updates in this PR.

---

1-1: Submodule commit verified as valid and accessible.

The commit d4ad9aa4bc6889b9c49cb34d703c7f346ab48778 exists in the zenstackhq/v3-doc-server-adapter repository and is accessible. The commit message is "update to latest," authored by ymc9 on 2025-11-18. The submodule is correctly pinned in the repository's git index.