Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions .github/dependabot.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# To get started with Dependabot version updates, you'll need to specify which
# package ecosystems to update and where the package manifests are located.
# Please see the documentation for all configuration options:
# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates

version: 2
updates:
- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: "monthly"
groups:
github-actions:
patterns:
- "*"
- package-ecosystem: "pip"
directory: "/"
schedule:
interval: "monthly"
groups:
python:
patterns:
- "*"
Comment on lines +21 to +23
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

While grouping all Python dependencies into a single python group is a good start, it can lead to very large and hard-to-review pull requests from Dependabot, especially as the number of dependencies grows. If one dependency update in the group causes a failure, the entire update is blocked.

Consider splitting dependencies into more granular, logical groups. For example, you could group core machine learning frameworks separately from development and testing tools. This will result in smaller, more manageable PRs.

Here is a suggested grouping:

      # Group core ML dependencies
      ml-core:
        patterns:
          - "tensorflow*"
          - "torch"
          - "jax*"
          - "keras"
          - "numpy"
          - "ml-dtypes"
          - "absl-py"
      # Group development and build tools
      dev-tools:
        patterns:
          - "mypy"
          - "ruff"
          - "pytest*"
          - "pre-commit"
          - "build"
          - "namex"

ignore:
# 2.19.1 is the last version of the TensorFlow that supports TPUs.
- dependency-name: "tensorflow-tpu"
4 changes: 2 additions & 2 deletions requirements-jax-cuda.txt
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
# Tensorflow cpu-only version.
tensorflow-cpu>=2.20.0
tensorflow-cpu

# Torch cpu-only version.
--extra-index-url https://download.pytorch.org/whl/cpu
torch>=2.1.0
torch

# Jax with cuda support.
--find-links https://storage.googleapis.com/jax-releases/jax_cuda_releases.html
Expand Down
2 changes: 1 addition & 1 deletion requirements-jax-tpu.txt
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# Tensorflow cpu-only version.
tensorflow-cpu>=2.20.0
tensorflow-cpu

# Jax with TPU support.
jax[tpu]
Expand Down
2 changes: 1 addition & 1 deletion requirements-tensorflow-cuda.txt
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ tensorflow[and-cuda]

# Torch cpu-only version.
--extra-index-url https://download.pytorch.org/whl/cpu
torch>=2.1.0
torch

# Jax cpu-only version.
jax[cpu]
Expand Down
8 changes: 4 additions & 4 deletions requirements.txt
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
# Tensorflow.
tensorflow-cpu>=2.20.0;sys_platform != 'darwin'
tensorflow>=2.20.0;sys_platform == 'darwin'
tensorflow-cpu;sys_platform != 'darwin'
tensorflow;sys_platform == 'darwin'

# Torch.
--extra-index-url https://download.pytorch.org/whl/cpu
torch>=2.9.0
torch

# Jax.
jax[cpu]>=0.7.0
jax[cpu]
jax-tpu-embedding;sys_platform == 'linux' and platform_machine == 'x86_64'

# pre-commit checks (formatting, linting, etc.)
Expand Down
Loading