Repository navigation
fix: require XGBoost 3.2 for pandas 3 - #1141
Merged
Merged
Conversation
Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com> Signed-off-by: Egor Dmitriev <egor.dmitriev@alliander.com>
|
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
2 participants
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?
Prevents OpenSTEF’s XGBoost extras from resolving to versions that do not preserve pandas 3 DataFrame feature names. The regression test now lives with the OpenSTEF XGBoost forecaster tests, and the public lockfile was regenerated through the internal-index conversion workflow and converted back to PyPI URLs.
Closes #
Type of change
Breaking changes checklist
Checklist
poe all --checkpasses locally (blocked by unavailable files.pythonhosted.org access while building hatchling)