update submodule

[yi-xmu]

Summary by CodeRabbit

• Chores
  • Updated an internal submodule pointer. There are no code changes to the parent repository, no modifications to public APIs, and no user-facing behavior changes. Low-risk maintenance; no action required from users and existing integrations remain compatible.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6bc1f38b-6a71-4459-bd71-f4a25248b590

📥 Commits

Reviewing files that changed from the base of the PR and between a9ae705 and 45b33a5.

📒 Files selected for processing (1)

• src/mongo/db/modules/eloq/data_substrate

✅ Files skipped from review due to trivial changes (1)

• src/mongo/db/modules/eloq/data_substrate

---

Walkthrough

Updated the git submodule pointer for src/mongo/db/modules/eloq/data_substrate from commit 985017e22aa50e7b1308931bc8b9ab24106a8bcd to 93d102a36500b6d82a0d546e8e2b6a5259fd37c5; no other repository files or public APIs changed.

Changes

Cohort / File(s)	Summary
Submodule Reference Update src/mongo/db/modules/eloq/data_substrate	Advanced submodule commit pointer from 985017e22aa50e7b1308931bc8b9ab24106a8bcd to 93d102a36500b6d82a0d546e8e2b6a5259fd37c5; no direct code or API changes in this repository.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• update submodule #318: Updates the same src/mongo/db/modules/eloq/data_substrate submodule pointer.
• update submodule #470: Previously advanced the pointer to 985017e..., which this PR now advances from.
• Update submodule for update datasyncscan execution #384: Another PR updating the same submodule reference to a different commit.

Suggested reviewers

• liunyl

Poem

🐰 I hopped along the repo trail,
A hash was nudged, a tiny sail,
No code rewired, no APIs bent,
Just a submodule's journey sent. 🌿

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'update submodule' is vague and generic, using non-descriptive language that doesn't convey which submodule was updated or why.	Consider using a more specific title such as 'Update data_substrate submodule to latest commit' to clarify which submodule was updated and provide context.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

---

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