Temporarily lock pyomo to v6.9.5 due to performance regression

[idelder]

see Pyomo/pyomo#3971

Recommend that, until this pyomo issue is resolved or someone finds a way around it (e.g., specifying sort params for all components in Temoa), we lock pyomo to version 6.9.5.

Temporary solution to avoid new Temoa users being put off by models that don't solve.

Summary by CodeRabbit

• Chores
  • Updated Pyomo to version 6.9.5 for consistent project environments.
  • Added the required PLY package to installation requirements.
  • Refreshed dependency lock files and package verification hashes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 3392427f-ca76-4ff2-97ed-b309543282fc

📥 Commits

Reviewing files that changed from the base of the PR and between 138ce95 and 24fc6d6.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• pyproject.toml
• requirements-dev.txt
• requirements.txt

💤 Files with no reviewable changes (1)

• requirements-dev.txt

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.

---

Walkthrough

Changes

Dependency pinning

Layer / File(s)	Summary
Update project dependency contract pyproject.toml	Changes the main pyomo dependency from a minimum-version constraint to pyomo==6.9.5.
Synchronize exported requirements requirements.txt, requirements-dev.txt	Pins pyomo to 6.9.5 with updated hashes and adds hashed ply==3.11 entries attributed to pyomo.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 24fc6

This change locks Pyomo to 6.9.5 and updates the dependency files consistently to avoid the reported performance regression. No actionable merge-blocking risk remains beyond normal checks and review.

Suggested reviewers: jdecarolis

🚥 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 clearly and concisely describes the main change: temporarily pinning Pyomo to version 6.9.5 to address a performance regression.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[jdecarolis]

@idelder -- can you make the target branch unstable? If I merge directly to main, then dependency canary will keep upgrading pyomo and will undo the version lock when we merge unstable to main. I think we're close to merging unstable into main (minus PR #361)

[idelder]

Done