Repository navigation
chore(deps): regenerate uv.lock for v0.2.3 and ragas 0.4.x - #45
Merged
Merged
Conversation
The committed lockfile was last regenerated at v0.1.3 (April 13) and never refreshed through the v0.2.0 to v0.2.3 releases. It still pinned the three rag-forge packages at 0.1.3 and ragas at 0.2.15, while pyproject requires ragas>=0.4,<0.6. CI and local runs use non-strict `uv sync`, so uv silently re-resolved on every run and nothing broke, but installs were not reproducible and `uv sync --locked` would fail. Regenerated with `uv lock`. Changes: rag-forge-core, rag-forge-evaluator and rag-forge-observability move to 0.2.3; ragas moves to 0.4.3 and pulls in instructor, aiolimiter, pillow and scikit-network; voyageai 0.5.0 is added for the ragas-voyage extra. No source changes. Verified: `uv sync --all-packages --locked` succeeds; pytest 606 passed, 14 skipped; typecheck, lint, build and vitest all clean.
|
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Regenerates
uv.lockso it matches whatpyproject.tomlactually declares. Lockfile only, no source changes.ragas-voyageextra)Why
The lockfile was last regenerated at v0.1.3 on 13 April and never refreshed through v0.2.0 to v0.2.3, even though the packages were bumped and the RAGAS floor was raised to 0.4. CI runs
uv sync --all-packageswithout--locked, so uv has been silently re-resolving on every run. Nothing broke, but installs were not reproducible and anyone runninguv sync --lockedwould hit a hard error.Verification
uv lockis a no-op on top of this commituv sync --all-packages --lockedsucceedsuv run pytest: 606 passed, 14 skippedpnpm run typecheck,pnpm run lint,pnpm run build,pnpm run test:tsall cleanFollow-up to consider separately
Switching CI to
uv sync --all-packages --lockedwould turn future drift into a visible failure instead of a silent re-resolve.