Adding bump-version.py script

[jpchauvel]

• adding bump-version.py script
• bump version to 0.2.2

Summary by CodeRabbit

• New Release
  • Bumped package version to 0.2.2.
• Metadata
  • Added Repository URL to project metadata.
  • Refined license declaration format (no change to license itself).
• CI/CD
  • Renamed deployment job and enhanced publish step with a registry URL check.
• Tooling
  • Introduced a script to automate patch version bumps.
  • Added code style configuration (line length set to 79).
  • Updated development dependencies to support TOML writing.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Renames a GitHub Actions job and augments the publish step with a PyPI URL check. Adds a version-bump script that updates uv.lock and pyproject.toml and commits changes. Updates project metadata: version to 0.2.2, license table format, repository URL, build-system formatting, Black config, and adds tomli-w to dev deps.

Changes

Cohort / File(s)	Summary
Release workflow \.github/workflows/publish.yml	Renamed job docs to deploy; extended uv publish with --check-url https://pypi.org/simple.
Version bump tooling bin/bump-version.py	New script: increments patch version for package "edit-python-pe" in uv.lock and pyproject.toml; writes updates; stages and commits with message "bump version to {version}". Adds bump_version(version) and main().
Project metadata/config pyproject.toml	Version 0.2.1 → 0.2.2; moved license to [project.license]; added [project.urls].Repository; reformatted [build-system]; added [tool.black] (line-length 79); added tomli-w>=1.2.0 to dev dependency group; minor formatting cleanups.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    actor Dev as Developer
    participant Script as bump-version.py
    participant Lock as uv.lock
    participant PyProj as pyproject.toml
    participant Git as git

    Dev->>Script: Run script
    Script->>Lock: Read TOML, find "edit-python-pe" version
    Script->>Script: bump_version(old) => new
    Script->>Lock: Write updated version
    Script->>PyProj: Update [project].version
    Script->>Git: git add uv.lock pyproject.toml
    Script->>Git: git commit -m "bump version to {new}"
    Git-->>Script: Commit created
    Script-->>Dev: Exit (success)
    note right of Script: New automation for version bump and commit

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

I nudge the version, hop by hop,
A patch-sized leap—then git goes “pop!”
Workflows hum, the publish sings,
PyPI checked with tidy strings.
With whiskered grin and tidy TOML,
I ship my carrots—model formal. 🥕✨

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 9700307 and 0d0b593.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (3)

• .github/workflows/publish.yml (2 hunks)
• bin/bump-version.py (1 hunks)
• pyproject.toml (4 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch hotfix

---

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

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.