update default 'mappedfile' dependency commit

[pknowles]

Summary by CodeRabbit

• Chores
  • Updated internal dependencies to improve stability and performance.

[coderabbitai]

Walkthrough

Updated the Git commit reference for the decodeless_mappedfile dependency in CMakeLists.txt from commit a6e59f8b193298a16534beab694e30ae76d7f457 to a214250f70d218c055ef7b82f45f987183dceecf. No changes to build configuration or dependency fetching logic.

Changes

Cohort / File(s)	Summary
Dependency version update CMakeLists.txt	Updated FetchContent_Declare GIT_TAG for decodeless_mappedfile to newer commit hash

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A single hash, so small, so bright,
Dependencies march toward the light,
One commit forward, one step true,
The build stays strong, the project new!

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 pull request title "update default 'mappedfile' dependency commit" accurately describes the primary change in the changeset, which is updating the GIT_TAG for the decodeless_mappedfile dependency to a newer commit. The title is concise, clear, and specific—it uses descriptive language without vague terms or noise, making it easy for team members to understand the main point when scanning the git history. The reference to 'mappedfile' with quotes and "dependency commit" provides sufficient context about what is being modified.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dep_update

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2afa710 and 6f9b747.

📒 Files selected for processing (1)

• CMakeLists.txt (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build (windows-latest, Release, cl)

🔇 Additional comments (1)

CMakeLists.txt (1)

46-46: Commit verified: dependency update is valid.

The new commit a214250f70d218c055ef7b82f45f987183dceecf exists and introduces a targeted optimization for read-only file mappings on Linux, using MAP_SHARED instead of MAP_PRIVATE to avoid swap backing and prevent size limitations. The change is minimal, well-justified, and safe to merge.

[coderabbitai]

🧹 Nitpick | 🔵 Trivial

Consider documenting the dependency update reason.

To improve maintainability and traceability, consider adding a comment or referencing a changelog entry that explains why this dependency commit was updated (e.g., bug fixes, new features, security patches). This helps future reviewers understand the rationale for the change.

Example improvement:

      decodeless_mappedfile
      GIT_REPOSITORY https://github.com/decodeless/mappedfile.git
-     GIT_TAG a214250f70d218c055ef7b82f45f987183dceecf)
+     GIT_TAG a214250f70d218c055ef7b82f45f987183dceecf)  # Updated from a6e59f8: <reason>

Replace <reason> with a brief description of what changed (e.g., "fixes issue X" or "adds feature Y").

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents

In CMakeLists.txt around line 46, the pinned GIT_TAG commit for the dependency
lacks any explanation; add a one-line comment above or beside this GIT_TAG that
states the reason for the update (e.g., "update to commit a21425... — fixes
CVE-xxxx, or fixes bug #1234, or adds feature Y") and, if available, include a
short reference (PR/link or changelog entry) to the upstream change so future
reviewers can trace why this specific commit was chosen.