diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md index 145c0872..ade1c908 100644 --- a/docs/CHANGELOG.md +++ b/docs/CHANGELOG.md @@ -4,11 +4,7 @@ All notable changes to GemsPy are documented here. ## [Unreleased] -### Changed -- **Sequential mode carry-over length can now be controlled by the user through the parameter `carry-over-length` (default: `block-overlap`). This also fixes an incorrect stitching for `block-overlap >= 2`, where the previous hardcoded behaviour pinned block - *N+1*'s first timestep to block *N*'s **last** timestep — a different absolute timestep. -- **linopy upgraded to `>=0.9.0`** - the minimum supported Python version rises - to **3.11** accordingly (linopy 0.9 requires Python >= 3.11). +## [0.2.0] - 2026-08-24 ### Added - **Integer strategy and thermal heuristics** - components can now set @@ -23,9 +19,18 @@ All notable changes to GemsPy are documented here. expression language, usable in `extra-outputs` and port-field-definitions. Both take a bare variable identifier and return its *current* lower/upper bound post-solve — in particular reflecting mutations made by thermal heuristics (see "Integer strategy and thermal - heuristics" above), which previously had no way to be surfaced in results. Validated at - model-build time; using them inside constraints, binding-constraints, objective - contributions, or variable bounds raises a `ValueError`. + heuristics" above). + +### Changed +- **Sequential mode carry-over length is now user-controlled** through the new + `resolution.carry-over-length` parameter (default: `block-overlap`), which + sets how many of the shared leading timesteps of block *N+1* are pinned to + block *N*'s already-solved values. This also fixes an incorrect stitching + for `block-overlap >= 2`, where the previous hardcoded behaviour pinned block + *N+1*'s first timestep to block *N*'s **last** timestep — a different + absolute timestep. +- **linopy upgraded to `>=0.9.0`** - the minimum supported Python version rises + to **3.11** accordingly (linopy 0.9 requires Python >= 3.11). ### Fixed - **Standard library parsing now accepts hybrid port-type fields** - @@ -38,6 +43,8 @@ All notable changes to GemsPy are documented here. the fields are parsed and validated but otherwise ignored outside hybrid consumers. +--- + ## [0.1.3] - 2026-07-24 ### Added diff --git a/pyproject.toml b/pyproject.toml index 552fdd6f..3a34ad65 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta" [project] name = "gemspy" -version = "0.1.3" +version = "0.2.0" description = "Python interpreter for GEMS: modelling and simulation of complex energy systems under uncertainty" readme = "README.md" license = { file = "LICENSE" } diff --git a/uv.lock b/uv.lock index 1538ab23..0e7a115c 100644 --- a/uv.lock +++ b/uv.lock @@ -475,7 +475,7 @@ wheels = [ [[package]] name = "gemspy" -version = "0.1.3" +version = "0.2.0" source = { editable = "." } dependencies = [ { name = "antlr4-python3-runtime" },