chore: update submodules

[ymc9]

Summary by CodeRabbit

• Chores
  • Updated multiple submodule references to point to the latest commits across various projects. These are internal maintenance updates with no visible changes to end-user functionality or public APIs.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

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

Project	Deployment	Review	Updated (UTC)
zenstack-new-site	Ready	Preview, Comment	Dec 24, 2025 10:33am

[coderabbitai]

Walkthrough

Updates submodule commit references across nine zenstackhq/v3-doc-* subprojects without modifying code, public APIs, or control flow.

Changes

Cohort / File(s)

Summary

Submodule Pointer Updates 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, code-repos/zenstackhq/v3-doc-plugin, code-repos/zenstackhq/v3-doc-quick-start, code-repos/zenstackhq/v3-doc-server-adapter, code-repos/zenstackhq/v3-doc-tanstack-query

Commit hash references updated for each submodule; no functional code, API, or control-flow changes

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• docs: nestjs guide for v3 #526: Updates submodule commit references across multiple overlapping zenstackhq/v3-doc-* subprojects.
• doc: v3 tanstack-query docs #502: Updates the same v3-doc-tanstack-query submodule pointer.

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 'chore: update submodules' accurately describes the pull request, which updates references across nine submodules without introducing functional code changes.
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/submodules-update-2

---

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: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 110b09b and 345b55d.

📒 Files selected for processing (10)

• 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
• code-repos/zenstackhq/v3-doc-plugin
• code-repos/zenstackhq/v3-doc-quick-start
• code-repos/zenstackhq/v3-doc-server-adapter
• code-repos/zenstackhq/v3-doc-tanstack-query

🔇 Additional comments (10)

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

1-1: Verify coordinated submodule updates across all nine v3-doc- subprojects.*

This PR updates submodule pointers across nine repositories. Ensure that:

• The new commits are stable, tested, and intentionally selected
• All coordinated updates are compatible with each other
• No breaking changes are introduced to downstream consumers of these submodules
• The update has been validated in an integration environment if applicable

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

1-1: Submodule pointer update looks good.

This is a routine submodule reference update with no functional code changes. The commit hash format is valid. Ensure that:

• The new commit references are pushed to the respective upstream repositories
• All related submodules (v3-doc-orm, v3-doc-orm-computed-fields, v3-doc-orm-policy, etc.) are updated consistently as part of this PR

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

1-1: Verify the new commit hash is valid and inspect notable changes.

Ensure that the updated commit hash 00ed99fc07721ff736b6c31efcd9b7195f816a04 exists in the submodule repository and review if there are any breaking changes or significant updates that may impact users.

Since the validity and contents of the referenced commit cannot be confirmed from the repository context, consider:

• Verifying the commit exists in the upstream v3-doc-orm-polymorphism repository
• Reviewing the commit log or change summary to ensure no unexpected breaking changes
• Confirming the motivation for this update aligns with the PR objectives

If this is a routine pinning/synchronization update (e.g., pulling latest main/release), you may approve this; otherwise, request details on the nature of the changes in the updated submodule commits.

---

1-1: No submodule updates detected in this commit.

The submodule pointer hashes are identical between the previous commit and the current commit. All 10 submodule pointers (v3-doc-orm, v3-doc-orm-computed-fields, v3-doc-orm-policy, v3-doc-orm-polymorphism, v3-doc-orm-typed-json, v3-doc-orm-validation, v3-doc-plugin, v3-doc-quick-start, v3-doc-server-adapter, v3-doc-tanstack-query) remain unchanged. If submodule updates were intended, they have not been committed yet.

Likely an incorrect or invalid review comment.

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

1-1: Submodule reference update confirmed.

The commit pointer is updated as expected for routine submodule maintenance. Verify that the updated commit references have been validated and tested appropriately across all nine affected submodules.

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

1-1: All submodules were properly updated.

This commit adds all 10 v3-doc-* submodules (exceeding the 9 mentioned in the PR objectives). Each submodule reference was consistently added in the same commit, ensuring coherent version control across the subproject ecosystem.

code-repos/zenstackhq/v3-doc-quick-start (1)

1-1: The submodule updates are valid and coordinated across all submodules.

The new commit 9397c673de85dd85932ce4ac38e03cb0fb8de8c3 for v3-doc-quick-start is confirmed and currently set in the repository. All 10 documented submodules have been updated with distinct commit pointers (11 are defined in .gitmodules, with 10 present in the git index). The update is coordinated and complete.

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

1-1: Submodule update is valid and can be merged.

The commit hash d48998ef77ba2e59d0b545612fafa11071a41036 is valid and accessible in the upstream repository—it points to the current main branch. The previous commit also exists. This is a straightforward submodule pointer update with no additional verification needed.

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

1-1: Verify submodule commit references and coordination across all 9 submodule updates.

This PR updates commit pointers across nine submodules. Before merging, confirm the following:

1. All nine commit hashes are valid and reachable in their respective repositories.
2. The updates are fully coordinated—no incomplete partial updates across submodules.
3. If the updated submodules contain breaking changes, document required migration steps or post-merge validation.
4. Verify that the motivation for these updates (bug fixes, feature additions, security patches, etc.) is documented in the PR description or commit messages.

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

1-1: Submodule addition looks good.

This commit newly adds the v3-doc-orm-typed-json submodule (along with 9 others, for a total of 10 submodule additions/updates). The commit hash db774ab06fd28f2bbf027abf655ee8d30676aed1 is valid. Since submodule additions are low-risk metadata changes, this appears to be routine maintenance.