Bump version to 0.2.2

[kaidokert]

Summary by Sourcery

Bump the picojson crate version and update project documentation to reflect current stability and completed work.

Documentation:

• Clarify README stability wording and guidance for using alternative JSON libraries.

Chores:

• Update picojson crate version to 0.2.2 in Cargo.toml.
• Mark line/column number error reporting as completed in TODO.md.

Summary by CodeRabbit

• Documentation

  • Updated stability messaging in the README to more accurately reflect the library's current maturity level and direct users toward appropriate alternatives for production use cases.

• Chores

  • Incremented package version to 0.2.2.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation and metadata updates: README.md stability messaging refined for clarity, TODO.md task added to completed items, and picojson/Cargo.toml version incremented from 0.2.1 to 0.2.2. No functional changes introduced.

Changes

Cohort / File(s)	Summary
Documentation updates README.md, TODO.md	Reworded stability statements in README for conciseness; marked "Line/col numbers in errors" as completed task in TODO list
Version management picojson/Cargo.toml	Incremented package version from 0.2.1 to 0.2.2

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Version bump #40: Version bump to picojson/Cargo.toml — related through concurrent version management
• Bump version #54: Version increment in picojson/Cargo.toml — same manifest field modification
• Prepare the crate #8: Stability wording updates to README and Cargo.toml changes — overlaps in documentation and metadata refinement

Poem

🐰 With whiskers twitching, we hop along,
Refining words, making them strong,
Version bumped, the task is done,
Picojson hops toward the sun! 🌾

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: bumping the version from 0.2.1 to 0.2.2 in Cargo.toml, which is the primary functional change in this PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

[gemini-code-assist]

Summary of Changes

Hello @kaidokert, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on incrementing the project's version number to 0.2.2. Alongside this version update, the documentation has been slightly adjusted to better reflect the library's current stability status, and a previously planned feature for including line and column numbers in error messages has been marked as complete.

Highlights

• Version Bump: The project version has been updated from 0.2.1 to 0.2.2 in picojson/Cargo.toml.
• Documentation Update: The README.md file has been updated to refine the stability statement, changing 'not yet recommended for production use' to 'experimental' and 'For production code' to 'For battle-tested code'.
• Feature Completion: The TODO.md file now marks 'Line/col numbers in errors' as completed, indicating this feature has been implemented.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request bumps the version to 0.2.2, which is reflected in picojson/Cargo.toml. This version bump is justified by the completion of the 'Line/col numbers in errors' feature, as noted in TODO.md. The stability section in README.md has also been updated to reflect the project's growing maturity. The changes are logical and well-contained. I have one minor suggestion to improve the clarity of the README.md file.