Skip to content

release: spotforecast2 6.1.0 — support spotforecast2-safe 20.x#206

Merged
bartzbeielstein merged 7 commits into
mainfrom
develop
Jun 8, 2026
Merged

release: spotforecast2 6.1.0 — support spotforecast2-safe 20.x#206
bartzbeielstein merged 7 commits into
mainfrom
develop

Conversation

@bartzbeielstein

Copy link
Copy Markdown
Collaborator

Promote developmain to cut 6.1.0.

What ships

Why

sf2-safe 20.0.0 (ConfigEntsoe inherits ConfigMulti; n2o1 task removed) is live on PyPI. Releasing 6.1.0 lets the lecture (bart26k-lecture, pinned spotforecast2>=6.0.0,<7) resolve sf2-safe 20.0.0 transitively.

🤖 Generated with Claude Code

github-actions Bot and others added 7 commits June 7, 2026 19:44
Roadmap #5/#6 tooling baseline for spotforecast2:
- type checker: adopt Astral `ty` (sf2 had none); add [tool.ty]; run
  `ty check src/` non-blocking in CI.
- coverage: add [tool.coverage] with fail_under=60 ratchet (~65% today),
  enforced by the existing pytest --cov run.
- legacy lint: remove redundant .flake8 (not invoked; also dropped from
  runtime deps) + REUSE.toml entry. ([tool.ruff] already present.)
- docs (#5): new "API Reference In Sync" CI job fails on quartodoc drift.

Non-breaking, non-releasing (chore). Promotes to main with the next release.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…Multi

spotforecast2-safe 19.1.0 made ConfigMulti a dataclass, so every field
default is also a class attribute; deleting the instance attribute no
longer makes hasattr(config, "cv_block_size") False, which broke
test_steps_equal_predict_size_when_attr_absent. Wrap the config in a
proxy that genuinely hides the attribute (mirroring an older/third-party
PipelineConfig). cv_ts runtime is unaffected — it uses
getattr(config, "cv_block_size", None) or predict_size, handling absent,
None, and set identically. Also refresh uv.lock to safe 19.1.0.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…tooling-baseline

chore(tooling): add ty, coverage ratchet, docs-reference CI gate
Widen the spotforecast2-safe pin to >=19.0.0,<21 and lock to 20.0.0.

20.0.0 removes the spotforecast-safe-n2o1-cov-df console task (unused here) and
makes ConfigEntsoe inherit ConfigMulti. The full spotforecast2 suite was run
against 20.0.0 (editable overlay): 1171 passed, 0 failures — the inheritance
change is transparent (the only isinstance(ConfigMulti) check tests a ConfigMulti
instance) and nothing imports the removed task.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…upport-sf2-safe-20

feat(deps): support spotforecast2-safe 20.x
## [6.1.0-rc.1](v6.0.0...v6.1.0-rc.1) (2026-06-08)

### Features

* **deps:** support spotforecast2-safe 20.x ([40654f4](40654f4))
@bartzbeielstein

Copy link
Copy Markdown
Collaborator Author

🎉 This PR is included in version 6.1.0-rc.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@bartzbeielstein

Copy link
Copy Markdown
Collaborator Author

🎉 This PR is included in version 6.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants