fix: use cu128 PyTorch wheels for CUDA 12.9

[LalatenduMohanty]

PyTorch deprecated cu129 builds in favor of cu130, so the cu129 wheel index has no stable PyTorch 2.9 wheels. Switch to cu128 wheels which are binary-compatible within the CUDA 12.x family.

Closes #94

Summary by CodeRabbit

• Chores
  • Updated CUDA dependency configuration to align with current PyTorch wheel availability for improved installation reliability.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 1cfa5db and d7be445.

📒 Files selected for processing (1)

• cuda/12.9/app.conf

---

📝 Walkthrough

Walkthrough

Fixed the CUDA 12.9 PyPI extra index URL from the deprecated cu129 to cu128, with an explanatory comment documenting PyTorch's deprecation of cu129 wheels in favor of cu130.

Changes

Cohort / File(s)	Summary
CUDA 12.9 Configuration cuda/12.9/app.conf	Updated PIP_EXTRA_INDEX_URL from cu129 to cu128 with a clarifying comment about PyTorch's cu129 deprecation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: switching PyTorch wheels from cu129 to cu128 for CUDA 12.9 compatibility.
Linked Issues check	✅ Passed	The PR addresses the exact requirement from issue #94: updating the PIP_EXTRA_INDEX_URL from cu129 to cu128 and adding a compatibility note.
Out of Scope Changes check	✅ Passed	All changes directly address the linked issue objective; no out-of-scope modifications are present in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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.}

[shifa-khan]

LGTM/