build: switch to hatchling + hatch-vcs and add PyPI publish workflow#15
build: switch to hatchling + hatch-vcs and add PyPI publish workflow#15
Conversation
Replace uv_build with hatchling/hatch-vcs for automatic git-tag versioning. Add GitHub Actions workflow for publishing to PyPI on release via trusted publishing. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis pull request establishes automated CI/CD publishing infrastructure and implements dynamic versioning. It introduces a GitHub Actions workflow that builds and uploads packages to PyPI on release, switches to Hatch-based VCS versioning, and configures the build environment accordingly. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Replace uv_build with hatchling/hatch-vcs for automatic git-tag versioning. Add GitHub Actions workflow for publishing to PyPI on release via trusted publishing.
Summary by CodeRabbit