Bump version to 0.1.2 - #55
Conversation
The release workflow asserts the tag matches pyproject.toml, so v0.1.2 failed its version check six seconds in, before any build step ran. uv.lock carries the project's own version, so it is bumped in step or 'uv sync --locked' fails on the runners. Edited in place rather than regenerated, to avoid rewriting every registry entry.
|
Warning Review limit reached
Next review available in: 16 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
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 |
A developer with UV_INDEX_URL or a pip.conf mirror set had every uv command rewrite all 25 registry entries in uv.lock to that private index. Committing one breaks CI and any clone that cannot reach the mirror, and it was silent enough to need reverting before every commit. A default [[tool.uv.index]] in pyproject.toml takes precedence over the environment variable, so the lock stays reproducible for everyone without per-machine setup. Verified by running a full 'uv lock' with a mirror exported: the result is byte-identical to the committed lock, and every registry entry is pypi.org. The pre-commit guard stays as a backstop for anyone on an older uv.
1 participant
The v0.1.2 tag failed its release-workflow version check because
pyproject.tomlstill said0.1.1. Every job that runs the check died 6s in, so the macOS build never reached a real step.Bumps
pyproject.tomlto0.1.2and the matchingversionof the virtual project inuv.lock, whichuv sync --lockedvalidates on every runner.The lock is edited in place rather than regenerated: a full
uv lockrewrites all 25 registry entries to whatever index the local machine has configured. Verified withUV_INDEX_URL=https://pypi.org/simple uv sync --locked, which passes with only the single version line changed.After merge, the
v0.1.2tag needs to move to the new commit to re-trigger the release.