build: switch to hatch-vcs for automatic git-tag versioning#106
build: switch to hatch-vcs for automatic git-tag versioning#106
Conversation
Replace static version with dynamic version sourced from git tags via hatch-vcs. Update publish workflow with separate build/upload jobs and fetch-depth: 0 for full git history. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 57 minutes and 9 seconds. ⌛ 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)
✨ 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 |
Summary
version = "0.2.2"with dynamic versioning viahatch-vcs(git tags)[tool.hatch.version]and[tool.hatch.build.hooks.vcs]config topyproject.tomlfetch-depth: 0for full git historysrc/molify/_version.pyto.gitignoreSame build system as zincware/asebytes#15.
Test plan
uv buildproduces correctly versioned wheel and sdist_version.pyis generated and gitignored🤖 Generated with Claude Code