Skip to content

Bump version to 0.2.0#37

Merged
RadCod3 merged 2 commits into
mainfrom
release/v0.2.0
Jan 11, 2026
Merged

Bump version to 0.2.0#37
RadCod3 merged 2 commits into
mainfrom
release/v0.2.0

Conversation

@RadCod3
Copy link
Copy Markdown
Owner

@RadCod3 RadCod3 commented Jan 11, 2026

Summary

  • Update version from 0.1.0 to 0.2.0 in pyproject.toml

Changes

  • Prepare for release v0.2.0

This PR updates the version number in preparation for creating the v0.2.0 release tag.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jan 11, 2026

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

📝 Walkthrough

Walkthrough

The project version is bumped from 0.1.0 to 0.2.0 in pyproject.toml. No changes to dependencies, scripts, or other configuration settings.

Changes

Cohort / File(s) Summary
Version Update
pyproject.toml
Version property updated from 0.1.0 to 0.2.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hop, hop, and the version grows,
From point-one to point-two it goes,
A tiny change, but oh so sweet,
The project's progress is complete!
✨ Onward we bound, to newer heights,
With version bumps and coding flights!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and directly summarizes the main change: bumping the version to 0.2.0 in pyproject.toml.
Description check ✅ Passed The description is directly related to the changeset, explaining the version bump from 0.1.0 to 0.2.0 and its purpose for the v0.2.0 release.
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.


Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In @pyproject.toml:
- Line 11: pyproject.toml was bumped to version 0.2.0 but the tracked uv.lock
still pins lampyrid at 0.1.0; regenerate the lockfile so it matches the new
package version by running the lock command: run `uv lock` (or the project's
lock regeneration command) to update uv.lock, confirm lampyrid now shows 0.2.0
in the lockfile, and commit the updated uv.lock alongside the pyproject.toml
change.
📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 63f4303 and d7bd589.

📒 Files selected for processing (1)
  • pyproject.toml

Comment thread pyproject.toml
@RadCod3 RadCod3 merged commit e7055d6 into main Jan 11, 2026
4 checks passed
@coderabbitai coderabbitai Bot mentioned this pull request Jan 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant