feat(cli): bump version from 0.1.15 to 0.1.16

[zhravan]

Issue

Link to related issue(s):

---

Description

Short summary of what this PR changes or introduces.

---

Scope of Change

Select all applicable areas impacted by this PR:

• View (UI/UX)
• API
• CLI
• Infra / Deployment
• Docs
• Other (specify): ________

---

Screenshot / Video / GIF (if applicable)

Attach or embed screenshots, screen recordings, or GIFs demonstrating the feature or fix.

---

Related PRs (if any)

Link any related or dependent PRs across repos.

---

Additional Notes for Reviewers (optional)

Anything reviewers should know before testing or merging (e.g., environment variables, setup steps).

---

Developer Checklist

To be completed by the developer who raised the PR.

• Add valid/relevant title for the PR
• Self-review done
• Manual dev testing done
• No secrets exposed
• No merge conflicts
• Docs added/updated (if applicable)
• Removed debug prints / secrets / sensitive data
• Unit / Integration tests passing
• Follows all standards defined in Nixopus Docs

---

Reviewer Checklist

To be completed by the reviewer before merge.

• Peer review done
• No console.logs / fmt.prints left
• No secrets exposed
• If any DB migrations, migration changes are verified
• Verified release changes are production-ready

Summary by CodeRabbit

• Chores
  • Updated project version number.

[coderabbitai]

Walkthrough

The pull request updates the project version number in the CLI package configuration from 0.1.15 to 0.1.16. This is a packaging metadata change with no functional code modifications, runtime impact, or control flow changes.

Changes

Cohort / File(s)	Summary
Version Bump cli/pyproject.toml	Updated version field in [tool.poetry] metadata from 0.1.15 to 0.1.16

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(cli): bump version cli tool #335: Both PRs update package versions in cli/pyproject.toml with minor version bumps.

Suggested reviewers

• raghavyuva

Poem

🐰✨ A version hops forward, so small yet so bright,
From fifteen to sixteen, a step in the light,
No logic to change, just a number's small dance,
The CLI takes flight with its incremental prance! 🚀

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 "feat(cli): bump version from 0.1.15 to 0.1.16" is fully related to the main change in the changeset. The raw summary confirms that the only modification is a version bump in cli/pyproject.toml from 0.1.15 to 0.1.16, with no functional or runtime impact. The title is specific, concise, and uses conventional commit format with a clear scope (cli). A developer scanning the history would immediately understand that this PR contains a patch version bump for the CLI package.
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 ver-patch-1

---

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: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 37f5de2 and 46940d5.

📒 Files selected for processing (1)

• cli/pyproject.toml (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-and-package-macos (macos-13)

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Version bump looks good, but verify consistency across the codebase.

The patch-level version bump (0.1.15 → 0.1.16) follows semantic versioning and is appropriately minimal. However, ensure that:

1. Any other version references in the codebase (e.g., root pyproject.toml, setup.py, __version__ constants, git tags) are also updated
2. A changelog entry or release notes document the changes included in this patch

Run the following script to identify other potential version references in the codebase:

---

🏁 Script executed:

#!/bin/bash
# Description: Search for version references that may need updating

# Check for version strings in common locations
echo "=== Searching for version references ==="
rg -i "0\.1\.15|version\s*=" --type toml --type py --type yaml --type json | grep -v node_modules | head -20

# Check for __version__ in Python files
echo -e "\n=== Checking for __version__ constants ==="
rg "^__version__\s*=" --type py

# Check for git tags related to versioning
echo -e "\n=== Checking for git tags ==="
git tag | grep -E "^v?0\.1\." | sort -V | tail -5

Length of output: 1652

---

Version bump is incomplete—update package.json.

The version in cli/pyproject.toml has been updated to 0.1.16, but package.json still references the old version in multiple places:

• "cli-version": "0.1.15" must be updated to "0.1.16"
• Artifact references (e.g., nixopus_0.1.15_amd64.apk, nixopus-0.1.15-darwin-amd64.pkg) should be updated to use 0.1.16 if they represent current release artifacts

Ensure version consistency across both files before merging.

🤖 Prompt for AI Agents

In cli/pyproject.toml around line 3 and in package.json (search entire file for
occurrences), the pyproject version was bumped to 0.1.16 but package.json still
contains 0.1.15; update package.json "cli-version": "0.1.15" to "0.1.16", update
all artifact filenames that embed the old version (e.g.,
nixopus_0.1.15_amd64.apk, nixopus-0.1.15-darwin-amd64.pkg) to use 0.1.16, and
verify there are no other 0.1.15 references remaining (update any other version
fields or metadata to 0.1.16 so both files are consistent).