Repository navigation
feat(STEF-3398): tag and validate OpenSTEF model versions - #1148
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com>
Collaborator
Author
|
Closing this PR because it was opened before the author asked for publication. The feature branch and commit are retained; it can be reopened after explicit approval with the repository PR template completed. |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com>
Keep existing users unaffected by default during rollout. The PR plans to enable enforcement by default on 2026-11-19. Assisted-by: GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com>
|
MvLieshout
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



What does this PR do?
Adds OpenSTEF model-version provenance and opt-in compatibility checks for MLflow-backed models. Training runs are tagged with the installed
openstef-coreversion. Consumers can enable enforcement withMLFlowStorage(enforce_version_compatibility=True); incompatible or untagged runs are then rejected withOpenSTEFVersionCompatibilityErrorand excluded from reuse and model selection. Applications should preflight compatibility before fetching expensive forecast inputs; OpenSTEF’s model-load check is a later safety net.Rollout plan: compatibility enforcement is opt-in initially to avoid surprising existing users. We plan to make it enabled by default (opt-out) on 2026-11-19, one month after this change.
Closes #
Type of change
Breaking changes checklist
_migrate_statemigration patternMigration path for existing users:
No migration is required unless a consumer opts in. Before enforcement becomes enabled by default, existing untagged models should be retrained or enforcement explicitly disabled.
AI disclosure
Checklist
poe all --checkpasses locally (focused tests, lint, formatting, and type checks pass; full docs build has unrelated existing warnings/errors)git commit -s)feat: ...,fix: ...,feat!: ...for breaking changes)