Bump version 0.2.0

[pedrxlz]

Summary by CodeRabbit

• Chores
  • Updated project version from 0.1.2 to 0.2.0
  • Updated kos dependency version from 0.1.0 to 0.2.0

[coderabbitai]

Walkthrough

The pull request involves updating the version numbers in the Cargo.toml file for a Rust workspace. The workspace package version has been incremented from 0.1.2 to 0.2.0, and the kos dependency version has been similarly updated from 0.1.0 to 0.2.0. These changes suggest a version bump for the project and its internal dependency.

Changes

File	Change Summary
Cargo.toml	- Workspace package version updated from 0.1.2 to 0.2.0 - kos dependency version updated from 0.1.0 to 0.2.0

Poem

🐰 A Rabbit's Version Hop 🚀

From zero-point-one to zero-point-two we leap,
Cargo's version numbers now take a mighty sweep
Kos dependency joins the dance, version aligned
A small change that shows our code is refined!
Hop, hop, hooray for progress so bright! 🌟

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c8fd03f and d3559c9.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• Cargo.toml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: format

🔇 Additional comments (2)

Cargo.toml (2)

18-18: Verify if this is a breaking change.

The version bump from 0.1.2 to 0.2.0 indicates a minor version increment. According to semantic versioning, this suggests new features were added in a backward-compatible manner. Please confirm if this accurately reflects the changes in this release.

Run the following script to check the commit history for breaking changes:

✅ Verification successful

Version bump from 0.1.2 to 0.2.0 appears correct

The minor version increment (0.1.2 to 0.2.0) aligns with semantic versioning principles for non-breaking changes. No breaking changes were detected in the commit history or public API surface, suggesting this is a feature release that maintains backward compatibility.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check commit messages for breaking change indicators

# Look for breaking change indicators in commit messages
git log --oneline | rg -i "breaking|!:"

Length of output: 0

---

Script:

#!/bin/bash
# Check commit messages with different patterns and formats
git log --format="%B" | rg -i "feat!|BREAKING CHANGE|incompatible|major changes"

# Look for modified public interfaces and exported items
fd -e rs -e toml . -x cat {} | rg -i "^pub |^pub\("

Length of output: 13797

---

53-53: Consider updating kos-mobile version.

While the kos package version has been bumped to 0.2.0, kos-mobile remains at 0.1.0. Since both are workspace members, consider whether kos-mobile should also be updated to maintain version consistency across the workspace.

Run the following script to check for potential breaking changes in the kos package that might affect kos-mobile:

---

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

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.