bump version

[daichengxin]

Summary by CodeRabbit

• Chores
  • Version updated to 0.0.5 across package configuration and CLI tooling.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

Warning

Review limit reached

@daichengxin, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 57 minutes. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 59b2c129-8bbe-4d33-879a-132853ae359b

📥 Commits

Reviewing files that changed from the base of the PR and between 79f0c12 and 0bd7ce4.

📒 Files selected for processing (1)

• tests/test_imports.py

📝 Walkthrough

Walkthrough

The package version is bumped to 0.0.5 in three places: the version field in pyproject.toml, the __version__ string in onsite/__init__.py, and the click.version_option decorator in onsite/onsitec.py.

Changes

Version bump to 0.0.5

Layer / File(s)	Summary
Version string updates across project, package, and CLI pyproject.toml, onsite/__init__.py, onsite/onsitec.py	pyproject.toml version updated from 0.0.4 to 0.0.5; __version__ updated from 0.0.3 to 0.0.5; CLI click.version_option updated from 0.0.4 to 0.0.5.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 Hop, hop, hooray, version bumps today!
From 0.0.3 and 0.0.4 we leap away,
Three little files now all agree,
0.0.5 is where we want to be!
The rabbit stamps the number with a thump—
Nothing changed but just this little bump! 🥕

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'bump version' directly and accurately describes the main change across all three modified files—the version was incremented from 0.0.3/0.0.4 to 0.0.5 in package metadata and CLI configuration.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@onsite/__init__.py`:
- Line 3: The version assertion in tests/test_imports.py at line 21 is checking
for the old version "0.0.3" but the package version in onsite/__init__.py has
been bumped to "0.0.5". Update the test assertion that checks onsite.__version__
to expect "0.0.5" instead of "0.0.3" to match the new version constant.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 26bb9e6c-6fa3-42aa-ab56-0be8fe19e031

📥 Commits

Reviewing files that changed from the base of the PR and between 4d0093d and 79f0c12.

📒 Files selected for processing (3)

• onsite/__init__.py
• onsite/onsitec.py
• pyproject.toml