Bump version to v0.14.16.0

[justanwar]

No description provided.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 46eee34 and 4fcbd29.

📒 Files selected for processing (1)

• CMakeLists.txt

---

Walkthrough

Version metadata update in CMakeLists.txt incrementing the client version revision from 15 to 16 and resetting the build number from 2 to 0.

Changes

Cohort / File(s)	Summary
Version Metadata CMakeLists.txt	Updated CLIENT_VERSION_REVISION to 16 and CLIENT_VERSION_BUILD to 0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Bump version to v0.14.15.1 #1728: Modifies version metadata (CLIENT_VERSION_BUILD and COPYRIGHT_YEAR) in CMakeLists.txt.
• Bump version to v0.14.15.0 #1674: Updates CLIENT_VERSION_REVISION and CLIENT_VERSION_BUILD variables representing sequential version bumps.
• Bump version to v0.14.15.2 #1751: Modifies CLIENT_VERSION_BUILD and/or CLIENT_VERSION_REVISION in CMakeLists.txt.

Suggested reviewers

• ajaydono
• levonpetrosyan93
• psolstice

Poem

🐰 A version bump hops along the way,
Revision sixteen sees the light of day!
Build resets clean, a fresh new start,
Metadata magic—a developer's art!

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is empty, missing the mandatory 'PR intention' section that explains what the PR is intended to do.	Add a PR description explaining the purpose of this version bump, such as release notes, changelog entries, or the reason for the version increment.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating version metadata from v0.14.15.2 to v0.14.16.0 in CMakeLists.txt.
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
• Post copyable unit tests in a comment
• Commit unit tests in branch v0141600

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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