docs: drop already-released 0.9.0 entries from Upcoming release notes by FabianHofmann · Pull Request #916 · PyPSA/linopy

FabianHofmann · 2026-09-02T12:38:08Z

wrong release notes as a merge artefact from the large v1 merge

Note

The following content was generated by AI.

The Upcoming Version section listed features that already shipped in
0.9.0 and are already documented under the existing Version v0.9.0
section (each with a PR reference). The v1 semantics merge (#717) re-added
them under Upcoming as duplicates.

This removes the duplicates from Upcoming:

In-place / persistent solver updates (feat(persistent): in-place solver updates (Solver framework + HiGHS/Gurobi/Xpress/Mosek) #718)
Model.to_netcdf_linopy_version attribute (feat(io): stamp linopy version into netCDF export #780)
int32 internal labels (perf: default integer arrays to int32 for ~25% memory reduction #566)
add_variables(binary=True) bounds (LP file export silently drops per-element bounds on binary variables, diverging from direct API #776)
add_piecewise_formulation(active_fill=...) (add_piecewise_formulation: support a partial active gate (treat missing/null entries as always-active) #796)
groupby().sum() scatter performance (perf(groupby): unify scatter kernel over numpy and dask via apply_ufunc #802)
setter deprecations (feat(persistent): in-place solver updates (Solver framework + HiGHS/Gurobi/Xpress/Mosek) #718)

Only genuinely-unreleased items remain under Upcoming: the v1 arithmetic
semantics, the piecewise mask parameter, the v1 notebook docs, and the
multi-key groupby sort bugfix. The 0.9.1 and v0.9.0 sections are
untouched.

The #717 merge re-added the persistent solver, netcdf version attr, int32 labels, binary bounds, active_fill, groupby-scatter and setter deprecations under Upcoming, but these all shipped in 0.9.0 and are already documented there. Remove the duplicates, leaving only the unreleased v1 semantics work under Upcoming.

github-actions · 2026-09-02T12:41:24Z

Build cost — v1 vs legacy

v1 build peak & time relative to legacy, on this commit — not a comparison against master (that is CodSpeed).

peak — v1 / legacy	time — v1 / legacy

Full table (time + peak, mean)

benchmarks/drivers/test_build.py::test_build[basic-n=10]
time (s) peak (KiB) name mean │ mean ──────────────────────────────────────────────
(legacy) 0.07058 (1.07) │ 13.33 (1.00) (v1) 0.06569 (1.0) │ 13.30 (1.0) benchmarks/drivers/test_build.py::test_build[basic-n=250]
time (s) peak (MiB) name mean │ mean ──────────────────────────────────────────────
(legacy) 0.07693 (1.07) │ 11.09 (1.00) (v1) 0.07164 (1.0) │ 11.09 (1.0) benchmarks/drivers/test_build.py::test_build[cumsum-severity=0]
time (s) peak (KiB) name mean │ mean ─────────────────────────────────────────────
(legacy) 0.02984 (1.09) │ 15.17 (1.0) (v1) 0.02734 (1.0) │ 15.17 (1.0) benchmarks/drivers/test_build.py::test_build[cumsum-severity=100]
time (s) peak (MiB) name mean │ mean ─────────────────────────────────────────────
(legacy) 0.04576 (1.14) │ 44.93 (1.0) (v1) 0.04003 (1.0) │ 44.93 (1.0) benchmarks/drivers/test_build.py::test_build[cumsum-severity=50]
time (s) peak (MiB) name mean │ mean ─────────────────────────────────────────────
(legacy) 0.03375 (1.11) │ 11.51 (1.0) (v1) 0.03049 (1.0) │ 11.51 (1.0) benchmarks/drivers/test_build.py::test_build[expression_arithmetic-n=10]
time (s) peak (KiB) name mean │ mean ──────────────────────────────────────────────
(legacy) 0.07991 (1.03) │ 24.23 (1.10) (v1) 0.07732 (1.0) │ 22.05 (1.0) benchmarks/drivers/test_build.py::test_build[expression_arithmetic-n=250]
time (s) peak (MiB) name mean │ mean ──────────────────────────────────────────────
(legacy) 0.09301 (1.06) │ 15.64 (1.00) (v1) 0.08751 (1.0) │ 15.64 (1.0) benchmarks/drivers/test_build.py::test_build[knapsack-n=10000]
time (s) peak (KiB) name mean │ mean ───────────────────────────────────────────────
(legacy) 0.01976 (1.06) │ 752.15 (1.10) (v1) 0.01858 (1.0) │ 685.11 (1.0) benchmarks/drivers/test_build.py::test_build[knapsack-n=100]
time (s) peak (KiB) name mean │ mean ─────────────────────────────────────────────
(legacy) 0.01918 (1.06) │ 3.09 (1.34) (v1) 0.01818 (1.0) │ 2.30 (1.0) benchmarks/drivers/test_build.py::test_build[kvl_cycles-severity=0]
time (s) peak (MiB) name mean │ mean ───────────────────────────────────────────────
(legacy) 0.05583 (1.16) │ 126.16 (1.44) (v1) 0.04805 (1.0) │ 87.71 (1.0) benchmarks/drivers/test_build.py::test_build[kvl_cycles-severity=100]
time (s) peak (MiB) name mean │ mean ───────────────────────────────────────────────
(legacy) 0.05486 (1.25) │ 126.16 (1.44) (v1) 0.04403 (1.0) │ 87.71 (1.0) benchmarks/drivers/test_build.py::test_build[kvl_cycles-severity=50]
time (s) peak (MiB) name mean │ mean ───────────────────────────────────────────────
(legacy) 0.05534 (1.27) │ 126.16 (1.44) (v1) 0.04361 (1.0) │ 87.71 (1.0) benchmarks/drivers/test_build.py::test_build[masked-n=100]
time (s) peak (KiB) name mean │ mean ───────────────────────────────────────────────
(legacy) 0.04207 (1.0) │ 714.28 (1.0) (v1) 0.04222 (1.00) │ 785.32 (1.10) benchmarks/drivers/test_build.py::test_build[masked-n=10]
time (s) peak (KiB) name mean │ mean ─────────────────────────────────────────────
(legacy) 0.04173 (1.08) │ 4.40 (1.34) (v1) 0.03853 (1.0) │ 3.27 (1.0) benchmarks/drivers/test_build.py::test_build[merge_balance-severity=0]
time (s) peak (KiB) name mean │ mean ──────────────────────────────────────────────
(legacy) 0.3114 (1.03) │ 702.97 (1.10) (v1) 0.3013 (1.0) │ 639.22 (1.0) benchmarks/drivers/test_build.py::test_build[merge_balance-severity=100]
time (s) peak (MiB) name mean │ mean ────────────────────────────────────────────
(legacy) 0.3326 (1.06) │ 18.34 (1.0) (v1) 0.3133 (1.0) │ 18.34 (1.0) benchmarks/drivers/test_build.py::test_build[merge_balance-severity=50]
time (s) peak (MiB) name mean │ mean ───────────────────────────────────────────
(legacy) 0.3246 (1.0) │ 9.54 (1.0) (v1) 0.3294 (1.01) │ 9.54 (1.0) benchmarks/drivers/test_build.py::test_build[milp-n=10]
time (s) peak (KiB) name mean │ mean ─────────────────────────────────────────────
(legacy) 0.06242 (1.11) │ 3.64 (1.14) (v1) 0.05616 (1.0) │ 3.20 (1.0) benchmarks/drivers/test_build.py::test_build[milp-n=50]
time (s) peak (KiB) name mean │ mean ───────────────────────────────────────────────
(legacy) 0.06028 (1.08) │ 216.15 (1.10) (v1) 0.05598 (1.0) │ 195.76 (1.0) benchmarks/drivers/test_build.py::test_build[nodal_balance-severity=0]
time (s) peak (KiB) name mean │ mean ──────────────────────────────────────────────
(legacy) 0.03001 (1.13) │ 935.30 (1.0) (v1) 0.02666 (1.0) │ 935.30 (1.0) benchmarks/drivers/test_build.py::test_build[nodal_balance-severity=100]
time (s) peak (MiB) name mean │ mean ────────────────────────────────────────────
(legacy) 0.03149 (1.14) │ 9.66 (1.0) (v1) 0.02767 (1.0) │ 9.66 (1.0) benchmarks/drivers/test_build.py::test_build[nodal_balance-severity=50]
time (s) peak (MiB) name mean │ mean ────────────────────────────────────────────
(legacy) 0.03192 (1.14) │ 5.32 (1.0) (v1) 0.028 (1.0) │ 5.32 (1.0) benchmarks/drivers/test_build.py::test_build[piecewise-n=1000]
time (s) peak (KiB) name mean │ mean ──────────────────────────────────────────────
(legacy) 0.1451 (1.04) │ 891.72 (1.07) (v1) 0.1394 (1.0) │ 836.28 (1.0) benchmarks/drivers/test_build.py::test_build[piecewise-n=10]
time (s) peak (KiB) name mean │ mean ─────────────────────────────────────────────
(legacy) 0.1495 (1.05) │ 11.02 (1.03) (v1) 0.1423 (1.0) │ 10.67 (1.0) benchmarks/drivers/test_build.py::test_build[qp-n=1000]
time (s) peak (KiB) name mean │ mean ───────────────────────────────────────────────
(legacy) 0.04103 (1.06) │ 147.66 (1.06) (v1) 0.03854 (1.0) │ 139.84 (1.0) benchmarks/drivers/test_build.py::test_build[qp-n=10]
time (s) peak (KiB) name mean │ mean ─────────────────────────────────────────────
(legacy) 0.04119 (1.08) │ 2.57 (1.09) (v1) 0.03801 (1.0) │ 2.35 (1.0) benchmarks/drivers/test_build.py::test_build[rolling-severity=0]
time (s) peak (KiB) name mean │ mean ───────────────────────────────────────────────
(legacy) 0.03032 (1.11) │ 696.72 (1.14) (v1) 0.02741 (1.0) │ 611.13 (1.0) benchmarks/drivers/test_build.py::test_build[rolling-severity=100]
time (s) peak (MiB) name mean │ mean ──────────────────────────────────────────────
(legacy) 0.07405 (1.07) │ 137.97 (1.0) (v1) 0.06912 (1.0) │ 137.97 (1.0) benchmarks/drivers/test_build.py::test_build[rolling-severity=50]
time (s) peak (MiB) name mean │ mean ─────────────────────────────────────────────
(legacy) 0.04967 (1.11) │ 69.22 (1.0) (v1) 0.04478 (1.0) │ 69.22 (1.0) benchmarks/drivers/test_build.py::test_build[sos-n=1000]
time (s) peak (KiB) name mean │ mean ───────────────────────────────────────────────
(legacy) 0.03526 (1.13) │ 377.39 (1.04) (v1) 0.0311 (1.0) │ 363.14 (1.0) benchmarks/drivers/test_build.py::test_build[sos-n=10]
time (s) peak (KiB) name mean │ mean ─────────────────────────────────────────────
(legacy) 0.03467 (1.12) │ 3.10 (1.41) (v1) 0.03105 (1.0) │ 2.20 (1.0) benchmarks/drivers/test_build.py::test_build[sparse_network-n=10]
time (s) peak (KiB) name mean │ mean ──────────────────────────────────────────────
(legacy) 0.04101 (1.11) │ 28.94 (1.61) (v1) 0.03685 (1.0) │ 17.97 (1.0) benchmarks/drivers/test_build.py::test_build[sparse_network-n=250]
time (s) peak (MiB) name mean │ mean ──────────────────────────────────────────────
(legacy) 0.05213 (1.13) │ 37.95 (1.43) (v1) 0.04608 (1.0) │ 26.51 (1.0) benchmarks/drivers/test_build.py::test_build[storage-n=10]
time (s) peak (KiB) name mean │ mean ───────────────────────────────────────────────
(legacy) 0.08087 (1.00) │ 397.39 (1.0) (v1) 0.08057 (1.0) │ 414.56 (1.04) benchmarks/drivers/test_build.py::test_build[storage-n=250]
time (s) peak (MiB) name mean │ mean ─────────────────────────────────────────────
(legacy) 0.08583 (1.0) │ 9.62 (1.0) (v1) 0.09001 (1.05) │ 9.90 (1.03)

📊 Interactive plots + CSV: download the semantics-report-v1-vs-legacy artifact from this run.

_{Report-only · not a gate · refreshed on every push · obsolete once legacy is dropped.}

codspeed-hq · 2026-09-02T12:42:35Z

Merging this PR will regress 2 benchmarks

⚠️

Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.
Open the report in CodSpeed to investigate

⚡ 2 improved benchmarks
❌ 2 regressed benchmarks
✅ 171 untouched benchmarks
⏩ 175 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	`BASE`	`HEAD`	Efficiency
❌	Memory	`test_to_lp[rolling-severity=50]`	356.2 MB	429.7 MB	-17.1%
❌	Memory	`test_to_lp[nodal_balance-severity=50]`	2.9 MB	3.3 MB	-12.06%
⚡	Memory	`test_to_lp[masked-n=100]`	2.7 MB	2.1 MB	+30.05%
⚡	Memory	`test_to_lp[storage-n=250]`	35.8 MB	32.3 MB	+11.06%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

_{Comparing fix/release-notes-0.9.1 (50385f1) with master (28be80f)}

175 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

FabianHofmann merged commit a64b657 into masterSep 2, 2026
11 of 12 checks passed

FabianHofmann deleted the fix/release-notes-0.9.1 branch September 2, 2026 12:39

Navigation Menu

Uh oh!

docs: drop already-released 0.9.0 entries from Upcoming release notes - #916

docs: drop already-released 0.9.0 entries from Upcoming release notes#916
FabianHofmann merged 1 commit into
masterfrom
fix/release-notes-0.9.1

FabianHofmann commented Sep 2, 2026•
edited
Loading

Uh oh!

Uh oh!

github-actionsBot commented Sep 2, 2026

Uh oh!

codspeed-hqBot commented Sep 2, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

FabianHofmann commented Sep 2, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

github-actionsBot commented Sep 2, 2026

Build cost — v1 vs legacy

Uh oh!

codspeed-hqBot commented Sep 2, 2026

Merging this PR will regress 2 benchmarks

Performance Changes

Footnotes

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

FabianHofmann commented Sep 2, 2026•
edited
Loading