Pin XGBoost due to incompatibility with current released sklearnex#194
Merged
david-cortes-intel merged 2 commits intoIntelPython:mainfrom Nov 5, 2025
Merged
Conversation
david-cortes-intel
requested review from
Vika-F,
avolkov-intel and
razdoburdin
david-cortes-intel
requested review from
Alexsandruss and
ethanglaser
as code owners
ethanglaser
approved these changes
Nov 5, 2025
Contributor
ethanglaser
left a comment
ethanglaser
left a comment
There was a problem hiding this comment.
Thanks, lets remember to update once compatible sklearnex is available
Merged
2 tasks
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.
Description
PR avoids pulling the latest version of xgboost, which is incompatible with the current released version of daal4py from sklearnex. The fix on the daal4py side is already merged into the main branch, but the CI jobs here pull the release packages from PyPI instead of building from the main branch. Hence, this workaround could be removed once 2025.10 is released, but will be needed in the meantime.
Checklist:
Completeness and readability
Testing