🐛 Cap PennyLane version#139
Conversation
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
📝 WalkthroughSummary by CodeRabbitChores
WalkthroughThis PR pins PennyLane to versions ChangesPennyLane Compatibility Pinning for Catalyst v0.14.1
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches✨ Simplify code
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 |
burgholzer
left a comment
There was a problem hiding this comment.
I think it would be slightly cleaner to also provide a lower bound for the pennylane dependency here. Most likely, pennylane~=0.44.0 (or pennylane~=0.44.1) is the right thing here.
Otherwise this LGTM
Description
This PR caps the PennyLane version to <0.45
The reason for this change is that CI started failing with
pennylane-catalyst==0.14.1, which allowspennylane>=0.44.1without an upper bound. Fresh builds can therefore resolvepennylane==0.45.0, but Catalyst 0.14.1 still importspennylane.transforms.core.transform_dispatcher, which was removed in PennyLane 0.45.This change adds an explicit
pennylane<0.45constraint.Assisted-by: GPT-5.5 via Codex
Checklist
If PR contains AI-assisted content:
Assisted-by: [Model Name] via [Tool Name]footer.