Skip to content

Conversation

@Pajaraja
Copy link
Collaborator

@Pajaraja Pajaraja commented Oct 22, 2025

Add a requirements.lock.txt file based on environment file to avoid problems with second order dependencies.

We should add checksums to the libraries at a later date. Currently it fails due to different settings for torch when working in a CPU and CUDA environment.

@Pajaraja Pajaraja requested a review from Copilot October 22, 2025 14:32
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR introduces a lock file approach for Python dependencies by replacing direct environment file usage with a generated requirements.lock.txt file to ensure reproducible builds with pinned second-order dependencies.

  • Adds a comprehensive requirements.lock.txt with 486 pinned dependencies generated via pip-compile
  • Updates CI workflows to install from the lock file instead of environment.txt
  • Maintains backward compatibility by referencing the original environment.txt in the lock file

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
runtime/requirements.lock.txt New lock file containing all pinned first and second-order dependencies
.github/workflows/runtime-test.yml Updates test workflow to install from lock file
.github/workflows/publish-to-pypi.yml Updates publish workflow to install from lock file

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@Pajaraja Pajaraja merged commit ac75e61 into databricks:branch-0.2.20.11 Oct 23, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant