Bump version 0.2.2

[pedrxlz]

Summary by CodeRabbit

Release Notes v0.2.2

• New Features

  • Expanded support for numerous blockchain networks, including Binance Smart Chain, Polkadot, Sui, Avalanche, Arbitrum, and more
  • Added roadmap for future cryptocurrency support, including Litecoin, Dogecoin, Cosmos, and Solana

• Documentation

  • Enhanced README with clearer package descriptions and comprehensive network support information

• Chores

  • Version bump to 0.2.2 for workspace and dependencies

[coderabbitai]

Walkthrough

This pull request involves version updates in the Cargo.toml file and significant enhancements to the README.md. The Cargo.toml changes increment the workspace and kos dependency versions from 0.2.0 to 0.2.2. The README.md has been extensively updated to include a comprehensive list of newly supported blockchain networks and cryptocurrencies, along with more detailed package descriptions.

Changes

File	Change Summary
Cargo.toml	- Workspace package version updated from 0.2.0 to 0.2.2 - kos dependency version updated from 0.2.0 to 0.2.2
README.md	- Added 18+ supported blockchain networks (e.g., Binance Smart Chain, Polkadot, Sui) - Added 16+ cryptocurrencies under "Coming soon" section - Enhanced package descriptions for kos, kos-web, and kos-mobile

Possibly related PRs

• Bump version 0.2.0 #80: Version number updates in Cargo.toml similar to this PR

Suggested labels

configuration

Suggested reviewers

• gustavocbritto

Poem

🚀 A rabbit's version dance,
Cargo.toml takes a leap and prance!
Networks bloom like spring's delight,
Blockchain magic takes its flight! 🌈
Version two-point-two, hooray! 🐰

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

README.md (2)

50-50: Fix markdown heading formatting.

Remove the trailing colon to comply with markdown heading guidelines.

-#### Coming soon | Under development:
+#### Coming soon | Under development

🧰 Tools

🪛 Markdownlint (0.37.0)

50-50: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)

---

98-103: Fix package description formatting.

The package descriptions contain unnecessary colons and inconsistent spacing.

-`packages/kos/`: Core package implementing all cryptocurrency wallet operations, including cryptographic functions,
+`packages/kos` - Core package implementing all cryptocurrency wallet operations, including cryptographic functions,
-`packages/kos-web/`:  Package responsible for exporting kos functionality to JavaScript bindings, providing methods
+`packages/kos-web` - Package responsible for exporting kos functionality to JavaScript bindings, providing methods
-`packages/kos-mobile/`: Package responsible for exporting kos functionality to mobile platforms, providing bindings
+`packages/kos-mobile` - Package responsible for exporting kos functionality to mobile platforms, providing bindings

🧰 Tools

🪛 LanguageTool

[uncategorized] ~98-~98: Loose punctuation mark.
Context: ...# Packages (Monorepo) - packages/kos/: Core package implementing all cryptocur...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~100-~100: Loose punctuation mark.
Context: ...r each blockchain. - packages/kos-web/: Package responsible for exporting kos ...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~102-~102: Loose punctuation mark.
Context: ...mplementations. - packages/kos-mobile/: Package responsible for exporting kos f...

(UNLIKELY_OPENING_PUNCTUATION)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c945375 and 1882354.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• Cargo.toml (2 hunks)
• README.md (3 hunks)

🧰 Additional context used

🪛 Markdownlint (0.37.0)

README.md

50-50: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)

🪛 LanguageTool

README.md

[uncategorized] ~98-~98: Loose punctuation mark.
Context: ...# Packages (Monorepo) - packages/kos/: Core package implementing all cryptocur...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~100-~100: Loose punctuation mark.
Context: ...r each blockchain. - packages/kos-web/: Package responsible for exporting kos ...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~102-~102: Loose punctuation mark.
Context: ...mplementations. - packages/kos-mobile/: Package responsible for exporting kos f...

(UNLIKELY_OPENING_PUNCTUATION)

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

• GitHub Check: format

🔇 Additional comments (4)

Cargo.toml (2)

18-18: LGTM! Version bump is consistent.

The version update from 0.2.0 to 0.2.2 is consistently applied across both the workspace package version and the kos dependency.

Also applies to: 53-53

---

Line range hint 41-41: Verify reqwest version compatibility.

The reqwest version 0.12 seems to be beyond the latest known stable release.

Run this script to verify the version:

README.md (2)

3-5: LGTM! Introduction text formatting improved.

The introduction text has been split into multiple lines for better readability while maintaining the same meaning.

---

24-48: LGTM! Comprehensive list of supported networks.

The list of supported blockchain networks has been significantly expanded with clear naming conventions.