Project version 2.2.5.16

[Danielius1922]

No description provided.

[coderabbitai]

Walkthrough

The pull request updates the version number of the iotivity-lite project across multiple files. The version is incremented from 2.2.5.15 to 2.2.5.16, reflecting a new build iteration. This change is consistently applied in the CMakeLists.txt, include/oc_build_info.h, and port/linux/Makefile files, ensuring that all relevant components reflect the updated versioning information.

Changes

File	Change Summary
CMakeLists.txt	Project version updated from 2.2.5.15 to 2.2.5.16.
include/oc_build_info.h	Versioning information updated: build number from 15 to 16, hexadecimal version from 0x0202050F to 0x02020510, and version string from "2.2.5.15" to "2.2.5.16".
port/linux/Makefile	Project version updated from 2.2.5.15 to 2.2.5.16 and VERSION_BUILD from 15 to 16.

Possibly related PRs

• Fix project and build versions #645: This PR updates the project version in CMakeLists.txt and include/oc_build_info.h from 2.2.5.13 to 2.2.5.15, which is directly related to the versioning changes made in the main PR that increments the version from 2.2.5.15 to 2.2.5.16.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[ocf-conformance-test-tool]

🎉 Thank you for your code contribution! To guarantee the change/addition is conformant to the OCF Specification, we would like to ask you to execute OCF Conformance Testing of your change ☝️ when your work is ready to be reviewed.

---

ℹ️ To verify your latest change (19c7de5), label this PR with OCF Conformance Testing.

⚠️ Label is removed with every code change.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8650644 and 19c7de5.

📒 Files selected for processing (3)

• CMakeLists.txt (1 hunks)
• include/oc_build_info.h (1 hunks)
• port/linux/Makefile (1 hunks)

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

• CMakeLists.txt

🔇 Additional comments (4)

include/oc_build_info.h (3)

33-33: LGTM: Version build number incremented correctly.

The IOTIVITY_LITE_VERSION_BUILD has been properly incremented from 15 to 16, consistent with the PR objectives for version 2.2.5.16.

---

40-40: LGTM: Hexadecimal version number updated correctly.

The IOTIVITY_LITE_VERSION hexadecimal representation has been correctly updated from 0x0202050F to 0x02020510, accurately reflecting the new version 2.2.5.16.

---

41-41: LGTM: Version string updated correctly and consistent with other representations.

The IOTIVITY_LITE_VERSION_STRING has been properly updated from "2.2.5.15" to "2.2.5.16", consistent with the PR objectives and the other version representations in this file.

To ensure consistency across all version representations, let's run the following verification script:

port/linux/Makefile (1)

9-15: Version number updated correctly.

The project version has been incremented from 2.2.5.15 to 2.2.5.16. This change is correctly reflected in both the comment and the VERSION_BUILD variable.

-# project version: 2.2.5.15
+# project version: 2.2.5.16
 VERSION_MAJOR = 2
 VERSION_MINOR = 2
 VERSION_PATCH = 5
-VERSION_BUILD = 15
+VERSION_BUILD = 16
 VERSION = $(VERSION_MAJOR).$(VERSION_MINOR).$(VERSION_PATCH).$(VERSION_BUILD)

The VERSION variable is correctly constructed using the updated components.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud