Build with uv

[jschlyter]

Summary by CodeRabbit

• Chores
  • Improved the automated testing process with more efficient triggers and streamlined test execution.
  • Updated the project’s build and dependency management configuration to enhance stability and compatibility.
  • Refined development workflows for testing, linting, and code formatting for a more consistent experience.

[coderabbitai]

Walkthrough

This pull request updates several project configuration files. The GitHub Actions workflow now triggers on both pull requests and pushes to the main branch, with the testing job streamlined to install and run tests using the new uv tool rather than relying on Poetry. The Makefile has been adapted to invoke commands with uv run and remove the virtual environment by deleting the .venv folder. The project configuration in pyproject.toml has been refactored from Poetry to a standard setuptools format with updated metadata and dependency management. Additionally, an ignore rule for *.egg-info files was added to .gitignore.

Changes

File(s)	Change Summary
.github/.../test.yml, Makefile, pyproject.toml	Updated command execution and dependency management: the workflow now installs uv via astral-sh/setup-uv@v5 and runs tests using uv run make test; the Makefile replaces poetry run with uv run for various tasks and removes the virtual environment using rm -fr .venv; the project configuration shifts from Poetry to setuptools with revised metadata and dependency definitions.
.gitignore	Added an entry to ignore files matching *.egg-info to exclude build/distribution metadata.

Sequence Diagram(s)

sequenceDiagram
  participant GitHubEvent as GitHub (Push/PR)
  participant Runner as GitHub Actions Runner
  participant UVInstaller as setup-uv Action
  participant TestRunner as Makefile

  GitHubEvent->>Runner: Trigger workflow on push/main or pull_request
  Runner->>UVInstaller: Run setup-uv to install latest uv
  UVInstaller-->>Runner: uv installed
  Runner->>TestRunner: Execute tests with "uv run make test"
  TestRunner-->>Runner: Return test results
  Runner->>GitHubEvent: Report status

Loading

Poem

I'm a rabbit dancing on fresh code trails,
Leaving Poetry in the dust as uv prevails,
Hopping through workflows with a skip and a cheer,
Makefiles and tests now run without fear.
In configuration fields where new standards gleam,
I celebrate these changes like a coding dream! 🐇
Cheers to smooth hops and a future so bright!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2238883 and 9455cf7.

⛔ Files ignored due to path filters (2)

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

📒 Files selected for processing (4)

• .github/workflows/test.yml (2 hunks)
• .gitignore (1 hunks)
• Makefile (1 hunks)
• pyproject.toml (1 hunks)

🔇 Additional comments (18)

.gitignore (1)

11-11: Added ignore entry for *.egg-info.

This entry ensures that Python package distribution metadata is not tracked, aligning with the shift from Poetry to setuptools.

Makefile (4)

4-4: Updated 'test' target with uv command.

Replacing the Poetry command with uv run pytest --ruff --ruff-format reflects the new toolchain integration correctly.

---

7-7: Updated 'lint' target with uv command.

Using uv run ruff check . is consistent with the new approach for executing linting tasks.

---

10-11: Updated 'reformat' target with uv commands.

The dual command usage (uv run ruff check --select I --fix . and uv run ruff format .) aligns with the project's new testing and formatting workflow.

---

16-16: Modified 'realclean' target for virtual environment removal.

Replacing poetry env remove --all with rm -fr .venv simplifies cleanup in line with the removal of Poetry dependency management.

.github/workflows/test.yml (2)

3-8: Updated workflow triggers.

The workflow now properly triggers on both pull_request events and pushes to the main branch, ensuring that tests run under the intended conditions with the new configuration.

---

29-40: Refined 'test' job steps to integrate uv.

The job now sets up Python using the latest actions/setup-python@v5, installs the latest uv via astral-sh/setup-uv@v5, and ultimately runs tests using uv run make test. This clearly reflects the migration from Poetry-based commands.

pyproject.toml (11)

1-7: Transition to standard project configuration.

The new [project] section now replaces the previous Poetry metadata. The updated authors format and the requires-python constraint ensure modern standards and better interoperability with setuptools.

---

8-10: Defined core dependency.

Including "structlog>=25.2.0" as the sole primary dependency is clean and minimal, keeping the project lightweight.

---

12-14: Configured repository URL.

The [project.urls] section correctly identifies the GitHub repository, which helps users and tooling find the source code.

---

15-25: Updated optional dependency for keymanager.

The version constraints for keymanager-related packages are clearly specified. It’s recommended to verify compatibility with the rest of the project, but the setup looks solid.

---

26-35: Refined opentelemetry dependency constraints.

The grouping and version constraints for the opentelemetry dependencies are well organized. Please double-check that these versions work seamlessly together.

---

37-47: Defined development dependency group.

Creating the [dependency-groups] section with a dev group streamlines installation of development tools like pytest, ruff, and uvicorn. This is a clear win for maintainability and testing.

---

49-51: Setuptools package configuration.

Specifying packages under [tool.setuptools] aligns the build process with the new configuration and ensures that the correct modules are packaged.

---

52-55: Updated build system backend.

Switching the build system requirements to ["setuptools>=77"] and the backend to "setuptools.build_meta" is appropriate given the removal of Poetry.

---

56-58: Ruff base configuration maintained.

The simple configuration with a line-length of 120 is preserved, ensuring consistency for code linting.

---

59-74: Retained Ruff linting selections and ignores.

The specific selection of linting rules (e.g., pycodestyle, Pyflakes, etc.) along with the ignore list is clear and aligns with project standards.

---

76-80: Preserved isort settings under Ruff configuration.

The settings for force-sort-within-sections, combine-as-imports, and split-on-trailing-comma are well maintained, reflecting adherence to the team's formatting guidelines.

---

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.
  • 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.
• @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.

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

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.