LCORE-446: Use uv tool to build and upload distribution archives

[tisnik]

Description

LCORE-446: Use uv tool to build and upload distribution archives

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up service version
• Bump-up dependent library
• Bump-up library or tool used for development (does not change the final image)
• CI configuration change
• Konflux configuration change
• Unit tests improvement
• Integration tests improvement
• End to end tests improvement

Related Tickets & Documents

• Related Issue #LCORE-446

Summary by CodeRabbit

• Chores
  • Updated build and upload commands to use a new tool for running Python scripts during distribution and upload processes.

[coderabbitai]

Walkthrough

The Makefile was updated to change the command prefix from pdm run to uv run in the distribution-archives and upload-distribution-archives targets. The underlying commands for building and uploading distribution archives remain the same, with only the tool used to invoke them being changed.

Changes

Cohort / File(s)	Change Summary
Makefile command prefix update Makefile	Replaced pdm run with uv run in the distribution-archives and upload-distribution-archives targets. No other modifications were made.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• LCORE-240: Makefile targets + updated documentation #222: Updates the same Makefile targets, indicating a direct connection to the changes in command prefixes for build and upload tasks.

Poem

A hop and a skip, a prefix anew,
From pdm to uv, the build commands flew.
The archives will rise, the uploads will run,
With Makefile refreshed, the work is well done!
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

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

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

Makefile (1)

86-88: Consider pre-flight check before running twine upload

uv run python -m twine upload --repository ${PYTHON_REGISTRY} dist/* assumes:

1. twine is present in the uv environment.
2. The dist/ directory contains at least one file. When it’s empty, shell globbing expands to the literal string dist/*, causing Twine to error with exit code 1.

A minimal safeguard:

-	uv run python -m twine upload --repository ${PYTHON_REGISTRY} dist/*
+	[ -n "$(ls -A dist 2>/dev/null)" ] && \
+	  uv run python -m twine upload --repository ${PYTHON_REGISTRY} dist/* || \
+	  echo "No distribution archives to upload"

Not strictly required, but it prevents noisy failures in automated pipelines.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 485affb and b362027.

📒 Files selected for processing (1)

• Makefile (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build-pr

🔇 Additional comments (1)

Makefile (1)

82-85: Verify uv environment has the build backend installed

Switching the target to uv run python -m build is fine as long as the build package lives inside the environment that uv run activates. Double-check that:

1. pyproject.toml lists build in [project.optional-dependencies.dev] (or similar), or
2. Your CI job explicitly installs it via uv pip install build.

Otherwise this target will silently fail with “No module named build”.