chore: update submodules - #535

Merged
ymc9 merged 3 commits into
mainfrom
chore/submodules-update-2
Dec 24, 2025
Merged

chore: update submodules#535
ymc9 merged 3 commits into
mainfrom
chore/submodules-update-2

Conversation

@ymc9

@ymc9ymc9 commented Dec 24, 2025•
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Member

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

vercelBot commented Dec 24, 2025•
edited
Loading

Copy link
Copy Markdown

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

ProjectDeploymentReviewUpdated (UTC)
zenstack-new-siteReadyReadyPreview, CommentDec 24, 2025 10:33am

@coderabbitai

coderabbitaiBot commented Dec 24, 2025•
edited
Loading

Copy link
Copy Markdown
Contributor

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

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title 'chore: update submodules' accurately describes the pull request, which updates references across nine submodules without introducing functional code changes.
Docstring Coverage✅ PassedNo 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

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

@ymc9
ymc9 merged commit 5405e06 into mainDec 24, 2025
3 checks passed
@ymc9
ymc9 deleted the chore/submodules-update-2 branch December 24, 2025 10:34
coderabbitai[bot]
coderabbitaiBot reviewed Dec 24, 2025
View reviewed changes

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment threadcode-repos/zenstackhq/v3-doc-orm-validation
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@coderabbitaicoderabbitai[bot]coderabbitai[bot] left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@ymc9
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
chore: update submodules - #535
Merged
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Dec 24, 2025
Merged
chore: update submodules#535
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Conversation
@ymc9
@ymc9ymc9
commented
Dec 24, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
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
vercelBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentReviewUpdated (UTC)
zenstack-new-siteReadyReadyPreview, CommentDec 24, 2025 10:33am
@coderabbitai
coderabbitaiBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
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
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title 'chore: update submodules' accurately describes the pull request, which updates references across nine submodules without introducing functional code changes.
Docstring Coverage✅ PassedNo 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
Comment @coderabbitai help to get the list of available commands and usage tips.
@ymc9
ymc9
merged commit 5405e06
into
mainDec 24, 2025

3 checks passed

@ymc9
ymc9
deleted the

chore/submodules-update-2

branch
December 24, 2025 10:34
coderabbitai[bot]
coderabbitaiBot
reviewed
Dec 24, 2025
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Comment threadcode-repos/zenstackhq/v3-doc-orm-validation
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@coderabbitaicoderabbitai[bot]coderabbitai[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@ymc9

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
chore: update submodules - #535
Merged
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Dec 24, 2025
Merged
chore: update submodules#535
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Conversation
@ymc9
@ymc9ymc9
commented
Dec 24, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
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
vercelBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentReviewUpdated (UTC)
zenstack-new-siteReadyReadyPreview, CommentDec 24, 2025 10:33am
@coderabbitai
coderabbitaiBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
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
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title 'chore: update submodules' accurately describes the pull request, which updates references across nine submodules without introducing functional code changes.
Docstring Coverage✅ PassedNo 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
Comment @coderabbitai help to get the list of available commands and usage tips.
@ymc9
ymc9
merged commit 5405e06
into
mainDec 24, 2025

3 checks passed

@ymc9
ymc9
deleted the

chore/submodules-update-2

branch
December 24, 2025 10:34
coderabbitai[bot]
coderabbitaiBot
reviewed
Dec 24, 2025
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Comment threadcode-repos/zenstackhq/v3-doc-orm-validation
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@coderabbitaicoderabbitai[bot]coderabbitai[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@ymc9

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
chore: update submodules - #535
Merged
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Dec 24, 2025
Merged
chore: update submodules#535
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Conversation
@ymc9
@ymc9ymc9
commented
Dec 24, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
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
vercelBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentReviewUpdated (UTC)
zenstack-new-siteReadyReadyPreview, CommentDec 24, 2025 10:33am
@coderabbitai
coderabbitaiBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
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
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title 'chore: update submodules' accurately describes the pull request, which updates references across nine submodules without introducing functional code changes.
Docstring Coverage✅ PassedNo 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
Comment @coderabbitai help to get the list of available commands and usage tips.
@ymc9
ymc9
merged commit 5405e06
into
mainDec 24, 2025

3 checks passed

@ymc9
ymc9
deleted the

chore/submodules-update-2

branch
December 24, 2025 10:34
coderabbitai[bot]
coderabbitaiBot
reviewed
Dec 24, 2025
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Comment threadcode-repos/zenstackhq/v3-doc-orm-validation
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@coderabbitaicoderabbitai[bot]coderabbitai[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@ymc9

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
chore: update submodules - #535
Merged
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Dec 24, 2025
Merged
chore: update submodules#535
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Conversation
@ymc9
@ymc9ymc9
commented
Dec 24, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
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
vercelBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentReviewUpdated (UTC)
zenstack-new-siteReadyReadyPreview, CommentDec 24, 2025 10:33am
@coderabbitai
coderabbitaiBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
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
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title 'chore: update submodules' accurately describes the pull request, which updates references across nine submodules without introducing functional code changes.
Docstring Coverage✅ PassedNo 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
Comment @coderabbitai help to get the list of available commands and usage tips.
@ymc9
ymc9
merged commit 5405e06
into
mainDec 24, 2025

3 checks passed

@ymc9
ymc9
deleted the

chore/submodules-update-2

branch
December 24, 2025 10:34
coderabbitai[bot]
coderabbitaiBot
reviewed
Dec 24, 2025
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Comment threadcode-repos/zenstackhq/v3-doc-orm-validation
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@coderabbitaicoderabbitai[bot]coderabbitai[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@ymc9

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
chore: update submodules - #535
Merged
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Dec 24, 2025
Merged
chore: update submodules#535
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Conversation
@ymc9
@ymc9ymc9
commented
Dec 24, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
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
vercelBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentReviewUpdated (UTC)
zenstack-new-siteReadyReadyPreview, CommentDec 24, 2025 10:33am
@coderabbitai
coderabbitaiBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
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
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title 'chore: update submodules' accurately describes the pull request, which updates references across nine submodules without introducing functional code changes.
Docstring Coverage✅ PassedNo 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
Comment @coderabbitai help to get the list of available commands and usage tips.
@ymc9
ymc9
merged commit 5405e06
into
mainDec 24, 2025

3 checks passed

@ymc9
ymc9
deleted the

chore/submodules-update-2

branch
December 24, 2025 10:34
coderabbitai[bot]
coderabbitaiBot
reviewed
Dec 24, 2025
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Comment threadcode-repos/zenstackhq/v3-doc-orm-validation
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@coderabbitaicoderabbitai[bot]coderabbitai[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@ymc9

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
chore: update submodules - #535
Merged
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Dec 24, 2025
Merged
chore: update submodules#535
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Conversation
@ymc9
@ymc9ymc9
commented
Dec 24, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
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
vercelBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentReviewUpdated (UTC)
zenstack-new-siteReadyReadyPreview, CommentDec 24, 2025 10:33am
@coderabbitai
coderabbitaiBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
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
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title 'chore: update submodules' accurately describes the pull request, which updates references across nine submodules without introducing functional code changes.
Docstring Coverage✅ PassedNo 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
Comment @coderabbitai help to get the list of available commands and usage tips.
@ymc9
ymc9
merged commit 5405e06
into
mainDec 24, 2025

3 checks passed

@ymc9
ymc9
deleted the

chore/submodules-update-2

branch
December 24, 2025 10:34
coderabbitai[bot]
coderabbitaiBot
reviewed
Dec 24, 2025
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Comment threadcode-repos/zenstackhq/v3-doc-orm-validation
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@coderabbitaicoderabbitai[bot]coderabbitai[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@ymc9

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
chore: update submodules - #535
Merged
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Dec 24, 2025
Merged
chore: update submodules#535
ymc9 merged 3 commits into
mainfrom 
chore/submodules-update-2
Conversation
@ymc9
@ymc9ymc9
commented
Dec 24, 2025•

edited by coderabbitai
Bot
Loading

Copy link


Copy Markdown

Member
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
vercelBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentReviewUpdated (UTC)
zenstack-new-siteReadyReadyPreview, CommentDec 24, 2025 10:33am
@coderabbitai
coderabbitaiBot
commented
Dec 24, 2025•

edited

Loading

Copy link


Copy Markdown

Contributor
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
Pre-merge checks and finishing touches
✅ Passed checks (3 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title 'chore: update submodules' accurately describes the pull request, which updates references across nine submodules without introducing functional code changes.
Docstring Coverage✅ PassedNo 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
Comment @coderabbitai help to get the list of available commands and usage tips.
@ymc9
ymc9
merged commit 5405e06
into
mainDec 24, 2025

3 checks passed

@ymc9
ymc9
deleted the

chore/submodules-update-2

branch
December 24, 2025 10:34
coderabbitai[bot]
coderabbitaiBot
reviewed
Dec 24, 2025
View reviewed changes
@coderabbitaicoderabbitaiBot
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Comment threadcode-repos/zenstackhq/v3-doc-orm-validation
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@coderabbitaicoderabbitai[bot]coderabbitai[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

1 participant

@ymc9