fix(compatibility): add missing torch 2.3.1 to Python matrix, add reg…

[tejask011]

Description

This PR fixes a compatibility matrix inconsistency where torch==2.3.1 was present in the CUDA compatibility matrix but missing from the Python compatibility matrix.

Because of the missing entry, the Compatibility Resolver treated torch 2.3.1 as an unknown version and skipped Python and CUDA compatibility validation. This allowed unsupported combinations to pass validation and generate invalid installation scripts.

The fix adds the missing FrameworkVersionEntry for torch 2.3.1 with the correct Python and CUDA support metadata. Additionally, regression tests have been added to ensure unsupported Python and CUDA versions are properly rejected and valid configurations continue to resolve successfully.

---

Related Issues

Fixes #987

---

Changes Made

• Added missing torch 2.3.1 entry to backend/app/compatibility/matrix/python.py
• Added regression tests for Python and CUDA compatibility validation
• Added a positive test case to verify valid torch 2.3.1 configurations resolve correctly
• Restored proper compatibility checks for torch 2.3.1

---

Verification

• Added unit tests
• Ran pytest tests/ successfully
• Manually verified resolver behavior for supported and unsupported combinations
• (If applicable) Generated scripts pass SafetyFilter

---

Documentation

• Updated docs/FEATURES.md (if adding a feature/profile)
• Updated CHANGELOG.md
• Code is fully documented and type-hinted

---

Screenshots (if applicable)

N/A – Backend-only change with no UI modifications.

Summary by CodeRabbit

• New Features

  • Added support for PyTorch 2.3.1 with Python 3.8–3.11 and CUDA 11.8, 12.1 compatibility.

• Tests

  • Added regression tests to validate compatibility resolution for PyTorch 2.3.1 across supported Python and CUDA versions.

[vercel]

@tejask011 is attempting to deploy a commit to the rishabhmishra0510-5147's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9d5b735b-c18e-4189-a4bc-9b05d99457d3

📥 Commits

Reviewing files that changed from the base of the PR and between 80ecef9 and 37d9166.

📒 Files selected for processing (2)

• backend/app/compatibility/matrix/python.py
• backend/tests/unit/compatibility/test_resolver.py

---

📝 Walkthrough

Walkthrough

This PR adds the missing PyTorch 2.3.1 entry to the Python compatibility matrix, documenting its supported Python and CUDA versions, and introduces three regression tests to verify the resolver now correctly validates compatibility checks for this version instead of silently bypassing them.

Changes

PyTorch 2.3.1 Compatibility Fix

Layer / File(s)	Summary
PyTorch 2.3.1 matrix entry backend/app/compatibility/matrix/python.py	Inserted a new FrameworkVersionEntry for torch 2.3.1 with supported Python versions 3.8–3.11 and CUDA versions 11.8, 12.1, positioned before the torch 2.4.0 entry.
Regression tests for torch 2.3.1 compatibility backend/tests/unit/compatibility/test_resolver.py	Added three async regression tests: one verifying the resolver rejects torch 2.3.1 with unsupported Python 3.12, one rejecting unsupported CUDA 12.4, and one confirming successful resolution for Python 3.11 + CUDA 12.1 with the correct cuda_variant.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• rishabh0510rishabh/EnvForage#309: Both PRs modify the Python compatibility matrix in backend/app/compatibility/matrix/python.py—main PR hardcodes a new torch 2.3.1 entry, while the retrieved PR refactors PYTHON_MATRIX to be JSON-driven—so they directly overlap in how the matrix entries (including torch 2.3.1) are defined/loaded.
• rishabh0510rishabh/EnvForage#180: Both PRs update the backend/app/compatibility/matrix/python.py compatibility data (PYTHON_MATRIX) for PyTorch version entries (main adds torch 2.3.1; retrieved adds torch 2.5.0/Python 3.13 support), impacting the same resolver compatibility lookup.

Suggested labels

level:intermediate

Suggested reviewers

• rishabh0510rishabh

Poem

🐰 A missing torch, now shining bright,
2.3.1 finds its rightful place,
Python versions guarded, CUDA checked with care,
The resolver breathes easier with validation's grace! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 75.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main changes: adding missing torch 2.3.1 to Python matrix and adding regression tests.
Linked Issues check	✅ Passed	All objectives from issue #987 are met: torch 2.3.1 added to Python matrix with correct Python/CUDA versions, and regression tests verify validation is restored.
Out of Scope Changes check	✅ Passed	All changes directly address the linked issue: adding torch 2.3.1 entry and tests for validating Python/CUDA compatibility.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🔍 PR Action Required

Hi @tejask011,

We detected some items on this Pull Request that require attention:

❌ Failing CI Checks

The following check runs or commit statuses are failing (ignoring vercel):

• Frontend Build & Lint
• Backend Tests

Please resolve the issues above to proceed.

---

Last updated: Thu, 11 Jun 2026 05:21:19 GMT

[tejask011]

🔍 PR Action Required

Hi @tejask011,

We detected some items on this Pull Request that require attention:

❌ Failing CI Checks

The following check runs or commit statuses are failing (ignoring vercel):

• Frontend Build & Lint
• Backend Tests

Please resolve the issues above to proceed.

Last updated: Thu, 11 Jun 2026 05:12:31 GMT

Both failing CI checks (Frontend Build & Lint and Backend Tests) are pre-existing failures on the main branch unrelated to this PR.
so please review this