chore: upgrade to linopy 0.7.0#173
Conversation
Replace the git-commit pin with the released linopy>=0.7.0, drop the xarray<2026.4.0 cap (PyPSA/linopy#647 fixes the Dataset-as-data_vars regression in 0.7.0), and silence the EvolvingAPIWarning emitted by `add_piecewise_formulation` so users don't see it on every solve — fluxopt absorbs that API-stability risk in its own changelog. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
📝 WalkthroughWalkthroughThis PR upgrades the project to use linopy 0.7.0+ from its published package instead of a pinned Git reference, loosens the xarray compatibility constraint, and suppresses the Changeslinopy Upgrade and Warning Handling
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📝 Generate docstrings
🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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 |
Codecov Report✅ All modified and coverable lines are covered by tests.
🚀 New features to boost your workflow:
|
Cosmetic — initial-version is only used at bootstrap (already past). Cleans up the last alpha reference touched by config; manifest and classifier left as-is so release-please drops the prerelease suffix on its own cycle. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Summary
2d2e851d,0.6.4.post1.dev80) with the releasedlinopy>=0.7.0. This unblocks PyPI publication — PyPI rejects direct URL deps, so the git pin was the actual blocker, not the alpha version suffix.xarray<2026.4.0cap — PyPSA/linopy#647 fixes the Dataset-as-data_vars regression in 0.7.0; xarray now resolves to 2026.4.0 locally.linopy.EvolvingAPIWarninginside_create_piecewise_constraintsso users don't see it on every solve — fluxopt owns the API-stability risk ofadd_piecewise_formulationand will surface it in its own changelog instead.-alpha.0frominitial-versionin.release-please-config.json(bootstrap-only field, no functional effect).Our existing
PiecewiseConversionwiring already matches the unified v0.7.0 API (PyPSA/linopy#638) —(expr, breaks)/(expr, breaks, sign)tuples,method="auto"|"sos2"|"incremental"|"lp",active=gate. No code changes needed there.The release-please manifest (
0.0.7-alpha.0) and the3 - Alphaclassifier are intentionally left alone — the next release-please cycle will drop the prerelease suffix on its own now thatprerelease/prerelease-typeare gone from the config (already done in #163).Test plan
uv sync --group devresolves linopy 0.7.0 + xarray 2026.4.0uv run pytest— 469 passed, 227 skipped (full piecewise suite green)uv run mypy src/— cleanuv run ruff check .— cleanEvolvingAPIWarningno longer appears in pytest warning summary🤖 Generated with Claude Code