Bump version to v0.14.16.2

[justanwar]

No description provided.

[codeant-ai]

CodeAnt AI is reviewing your PR.

[codeant-ai]

CodeAnt-AI Description

Bump version to v0.14.16.2

What Changed

• Updates the displayed build version from v0.14.16.1 to v0.14.16.2

Impact

✅ Correct version shown in the app
✅ Clearer release identification
✅ Easier support and update tracking

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: f499c641-de6b-45a7-9af8-e4dd97c9e782

📥 Commits

Reviewing files that changed from the base of the PR and between 7fabe1e and dfc9adc.

📒 Files selected for processing (1)

• CMakeLists.txt

---

Summary by CodeRabbit

• Chores
  • Updated the client build/version number from 1 to 2, so the app now reports the newer version in build and release information.

Walkthrough

This PR updates CLIENT_VERSION_BUILD in CMakeLists.txt from 1 to 2, incrementing the build number used to compose the project's version string.

Changes

Version Bump

Layer / File(s)	Summary
Update client build version CMakeLists.txt	CLIENT_VERSION_BUILD incremented from 1 to 2.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• firoorg/firo#1674: Both PRs modify CMakeLists.txt version components by changing CLIENT_VERSION_BUILD.
• firoorg/firo#1852: Both PRs modify CLIENT_VERSION_BUILD to bump the composed version string.
• firoorg/firo#1786: Both PRs modify CMakeLists.txt by changing CLIENT_VERSION_BUILD.

Suggested labels: build-system

Suggested reviewers: ajaydono, psolstice, levoncrypto, levonpetrosyan93

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No PR description was provided, so the required intention section is missing.	Add the required PR intention section and briefly describe the change; include the optional code changes brief if useful.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the change: a version bump to v0.14.16.2.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

---

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

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dfc9adc25f

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Include the build component in package metadata

Because this release changes only CLIENT_VERSION_BUILD, user-facing package metadata that is still derived from just major/minor/revision will not distinguish v0.14.16.2 from the previous v0.14.16.x builds: share/qt/Info.plist.in sets both CFBundleShortVersionString and CFBundleVersion to 0.14.16, and share/setup.nsi.in uses the same three-part ${VERSION} for the installer filename, ProductVersion/FileVersion, and uninstall DisplayVersion. In macOS/Windows release builds this leaves the new artifacts advertising 0.14.16 instead of 0.14.16.2, so update those derived version strings when bumping only the build component.

Useful? React with 👍 / 👎.