Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency mlflow to v2.19.0 #118

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 8, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
mlflow ==2.15.1 -> ==2.19.0 age adoption passing confidence

Release Notes

mlflow/mlflow (mlflow)

v2.19.0

Compare Source

We are excited to announce the release of MLflow 2.19.0! This release includes a number of significant features, enhancements, and bug fixes.

Major New Features
  • ChatModel enhancements - ChatModel now adopts ChatCompletionRequest and ChatCompletionResponse as its new schema. The predict_stream interface uses ChatCompletionChunk to deliver true streaming responses. Additionally, the custom_inputs and custom_outputs fields in ChatModel now utilize AnyType, enabling support for a wider variety of data types. Note: In a future version of MLflow, ChatParams (and by extension, ChatCompletionRequest) will have the default values for n, temperature, and stream removed. (#​13782, #​13857, @​stevenchen-db)

  • Tracing improvements - MLflow Tracing now supports both automatic and manual tracing for DSPy, LlamaIndex and Langchain flavors. Tracing feature is also auto-enabled for mlflow evaluation for all supported flavors. (#​13790, #​13793, #​13795, #​13897, @​B-Step62)

  • New Tracing Integrations - MLflow Tracing now supports CrewAI and Anthropic, enabling a one-line, fully automated tracing experience. (#​13903, @​TomeHirata, #​13851, @​gabrielfu)

  • Any Type in model signature - MLflow now supports AnyType in model signature. It can be used to host any data types that were not supported before. (#​13766, @​serena-ruan)

Other Features:

Bug fixes:

Documentation updates:

Small bug fixes and documentation updates:

#​13972, #​13968, #​13917, #​13912, #​13906, #​13846, @​serena-ruan; #​13969, #​13959, #​13957, #​13958, #​13925, #​13882, #​13879, #​13881, #​13869, #​13870, #​13868, #​13854, #​13849, #​13847, #​13836, #​13823, #​13811, #​13820, #​13775, #​13768, #​13764, @​harupy; #​13960, #​13914, #​13862, #​13892, #​13916, #​13918, #​13915, #​13878, #​13891, #​13863, #​13859, #​13850, #​13844, #​13835, #​13818, #​13762, @​B-Step62; #​13913, #​13848, #​13774, @​TomeHirata; #​13936, #​13954, #​13883, @​daniellok-db; #​13947, @​AHB102; #​13929, #​13922, @​Ajay-Satish-01; #​13857, @​stevenchen-db; #​13773, @​BenWilson2; #​13705, @​williamjamir; #​13745, #​13743, @​WeichenXu123; #​13895, @​chenmoneygithub; #​14023, @​theBeginner86

v2.18.0

Compare Source

We are excited to announce the release of MLflow 2.18.0! This release includes a number of significant features, enhancements, and bug fixes.

Python Version Update

Python 3.8 is now at an end-of-life point. With official support being dropped for this legacy version, MLflow now requires Python 3.9
as a minimum supported version.

Note: If you are currently using MLflow's ChatModel interface for authoring custom GenAI applications, please ensure that you
have read the future breaking changes section below.

Major New Features
  • 🦺 Fluent API Thread/Process Safety - MLflow's fluent APIs for tracking and the model registry have been overhauled to add support for both thread and multi-process safety. You are now no longer forced to use the Client APIs for managing experiments, runs, and logging from within multiprocessing and threaded applications. (#​13456, #​13419, @​WeichenXu123)

  • 🧩 DSPy flavor - MLflow now supports logging, loading, and tracing of DSPy models, broadening the support for advanced GenAI authoring within MLflow. Check out the MLflow DSPy Flavor documentation to get started! (#​13131, #​13279, #​13369, #​13345, @​chenmoneygithub, #​13543, #​13800, #​13807, @​B-Step62, #​13289, @​michael-berk)

  • 🖥️ Enhanced Trace UI - MLflow Tracing's UI has undergone
    a significant overhaul to bring usability and quality of life updates to the experience of auditing and investigating the contents of GenAI traces, from enhanced span content rendering using markdown to a standardized span component structure, (#​13685, #​13357, #​13242, @​daniellok-db)

  • 🚄 New Tracing Integrations - MLflow Tracing now supports DSPy, LiteLLM, and Google Gemini, enabling a one-line, fully automated tracing experience. These integrations unlock enhanced observability across a broader range of industry tools. Stay tuned for upcoming integrations and updates! (#​13801, @​TomeHirata, #​13585, @​B-Step62)

  • 📊 Expanded LLM-as-a-Judge Support - MLflow now enhances its evaluation capabilities with support for additional providers, including Anthropic, Bedrock, Mistral, and TogetherAI, alongside existing providers like OpenAI. Users can now also configure proxy endpoints or self-hosted LLMs that follow the provider API specs by using the new proxy_url and extra_headers options. Visit the LLM-as-a-Judge documentation for more details! (#​13715, #​13717, @​B-Step62)

  • ⏰ Environment Variable Detection - As a helpful reminder for when you are deploying models, MLflow now detects and reminds users of environment variables set during model logging, ensuring they are configured for deployment. In addition to this, the mlflow.models.predict utility has also been updated to include these variables in serving simulations, improving pre-deployment validation. (#​13584, @​serena-ruan)

Breaking Changes to ChatModel Interface
  • ChatModel Interface Updates - As part of a broader unification effort within MLflow and services that rely on or deeply integrate
    with MLflow's GenAI features, we are working on a phased approach to making a consistent and standard interface for custom GenAI
    application development and usage. In the first phase (planned for release in the next few releases of MLflow), we are marking
    several interfaces as deprecated, as they will be changing. These changes will be:

    • Renaming of Interfaces:
      • ChatRequestChatCompletionRequest to provide disambiguation for future planned request interfaces.
      • ChatResponseChatCompletionResponse for the same reason as the input interface.
      • metadata fields within ChatRequest and ChatResponsecustom_inputs and custom_outputs, respectively.
    • Streaming Updates:
      • predict_stream will be updated to enable true streaming for custom GenAI applications. Currently, it returns a generator with synchronous outputs from predict. In a future release, it will return a generator of ChatCompletionChunks, enabling asynchronous streaming. While the API call structure will remain the same, the returned data payload will change significantly, aligning with LangChain’s implementation.
    • Legacy Dataclass Deprecation:
      • Dataclasses in mlflow.models.rag_signatures will be deprecated, merging into unified ChatCompletionRequest, ChatCompletionResponse, and ChatCompletionChunks.

Other Features:

Bug fixes:

  • [Database] Cascade deletes to datasets when deleting experiments to fix a bug in MLflow's gc command when deleting experiments with logged datasets (#​13741, @​daniellok-db)
  • [Models] Fix a bug with Langchain's pyfunc predict input conversion (#​13652, @​serena-ruan)
  • [Models] Fix signature inference for subclasses and Optional dataclasses that define a model's signature (#​13440, @​bbqiu)
  • [Tracking] Fix an issue with async logging batch splitting validation rules (#​13722, @​WeichenXu123)
  • [Tracking] Fix an issue with LangChain's autologging thread-safety behavior (#​13672, @​B-Step62)
  • [Tracking] Disable support for running spark autologging in a threadpool due to limitations in Spark (#​13599, @​WeichenXu123)
  • [Tracking] Mark role and index as required for chat schema (#​13279, @​chenmoneygithub)
  • [Tracing] Handle raw response in openai autolog (#​13802, @​harupy)
  • [Tracing] Fix a bug with tracing source run behavior when running inference with multithreading on Langchain models (#​13610, @​WeichenXu123)

Documentation updates:

Small bug fixes and documentation updates:

#​13775, #​13768, #​13764, #​13744, #​13699, #​13742, #​13703, #​13669, #​13682, #​13569, #​13563, #​13562, #​13539, #​13537, #​13533, #​13408, #​13295, @​serena-ruan; #​13768, #​13764, #​13761, #​13738, #​13737, #​13735, #​13734, #​13723, #​13726, #​13662, #​13692, #​13689, #​13688, #​13680, #​13674, #​13666, #​13661, #​13625, #​13460, #​13626, #​13546, #​13621, #​13623, #​13603, #​13617, #​13614, #​13606, #​13600, #​13583, #​13601, #​13602, #​13604, #​13598, #​13596, #​13597, #​13531, #​13594, #​13589, #​13581, #​13112, #​13587, #​13582, #​13579, #​13578, #​13545, #​13572, #​13571, #​13564, #​13559, #​13565, #​13558, #​13541, #​13560, #​13556, #​13534, #​13386, #​13532, #​13385, #​13384, #​13383, #​13507, #​13523, #​13518, #​13492, #​13493, #​13487, #​13490, #​13488, #​13449, #​13471, #​13417, #​13445, #​13430, #​13448, #​13443, #​13429, #​13418, #​13412, #​13382, #​13402, #​13381, #​13364, #​13356, #​13309, #​13313, #​13334, #​13331, #​13273, #​13322, #​13319, #​13308, #​13302, #​13268, #​13298, #​13296, @​harupy; #​13705, @​williamjamir; #​13632, @​shichengzhou-db; #​13755, #​13712, #​13260, @​BenWilson2; #​13745, #​13743, #​13697, #​13548, #​13549, #​13577, #​13349, #​13351, #​13350, #​13342, #​13341, @​WeichenXu123; #​13807, #​13798, #​13787, #​13786, #​13762, #​13749, #​13733, #​13678, #​13721, #​13611, #​13528, #​13444, #​13450, #​13360, #​13416, #​13415, #​13336, #​13305, #​13271, @​B-Step62; #​13808, #​13708, @​smurching; #​13739, @​fedorkobak; #​13728, #​13719, #​13695, #​13677, @​TomeHirata; #​13776, #​13736, #​13649, #​13285, #​13292, #​13282, #​13283, #​13267, @​daniellok-db; #​13711, @​bhavya2109sharma; #​13693, #​13658, @​aravind-segu; #​13553, @​dsuhinin; #​13663, @​gitlijian; #​13657, #​13629, @​parag-shendye; #​13630, @​JohannesJungbluth; #​13613, @​itepifanio; #​13480, @​agjendem; #​13627, @​ilyaresh; #​13592, #​13410, #​13358, #​13233, @​nojaf; #​13660, #​13505, @​sunishsheth2009; #​13414, @​lmoros-DB; #​13399, @​Abubakar17; #​13390, @​KekmaTime; #​13291, @​michael-berk; #​12511, @​jgiannuzzi; #​13265, @​Ahar28; #​13785, @​Rick-McCoy; #​13676, @​hyolim-e; #​13718, @​annzhang-db; #​13705, @​williamjamir

v2.17.2

Compare Source

MLflow 2.17.2 includes several major features and improvements

Features:

Bug fixes:

Documentation updates:

Small bug fixes and documentation updates:

#​13569, @​serena-ruan; #​13595, @​BenWilson2; #​13593, @​mnijhuis-dnb;

v2.17.1

Compare Source

MLflow 2.17.1 includes several major features and improvements

Features:

Bug fixes:

Documentation updates:

Small bug fixes and documentation updates:

#​13293, #​13510, #​13501, #​13506, #​13446, @​harupy; #​13341, #​13342, @​WeichenXu123; #​13396, @​dvorst; #​13535, @​chenmoneygithub; #​13503, #​13469, #​13416, @​B-Step62; #​13519, #​13516, @​serena-ruan; #​13504, @​sunishsheth2009; #​13508, @​KamilStachera; #​13397, @​kriscon-db

v2.17.0

Compare Source

We are excited to announce the release of MLflow 2.17.0! This release includes several enhancements to extend the
functionality of MLflow's ChatModel interface to further extend its versatility for handling custom GenAI application use cases.
Additionally, we've improved the interface within the tracing UI to provide a structured output for retrieved documents,
enhancing the ability to read the contents of those documents within the UI.
We're also starting the work on improving both the utility and the versatility of MLflow's evaluate functionality for GenAI,
initially with support for callable GenAI evaluation metrics.

Major Features and notifications:
  • ChatModel enhancements - As the GenAI-focused 'cousin' of PythonModel, ChatModel is getting some sizable functionality
    extensions. From native support for tool calling (a requirement for creating a custom agent), simpler conversions to the
    internal dataclass constructs needed to interface with ChatModel via the introduction of from_dict methods to all data structures,
    the addition of a metadata field to allow for full input payload customization, handling of the new refusal response type, to the
    inclusion of the interface type to the response structure to allow for greater integration compatibility.
    (#​13191, #​13180, #​13143, @​daniellok-db, #​13102, #​13071, @​BenWilson2)

  • Callable GenAI Evaluation Metrics - As the intial step in a much broader expansion of the functionalities of mlflow.evaluate for
    GenAI use cases, we've converted the GenAI evaluation metrics to be callable. This allows you to use them directly in packages that support
    callable GenAI evaluation metrics, as well as making it simpler to debug individual responses when prototyping solutions. (#​13144, @​serena-ruan)

  • Audio file support in the MLflow UI - You can now directly 'view' audio files that have been logged and listen to them from within the MLflow UI's
    artifact viewer pane.

  • MLflow AI Gateway is no longer deprecated - We've decided to revert our deprecation for the AI Gateway feature. We had renamed it to the
    MLflow Deployments Server, but have reconsidered and reverted the naming and namespace back to the original configuration.

Features:

Bug fixes:

  • [Tracking] Fix tracing for LangGraph (#​13215, @​B-Step62)
  • [Tracking] Fix an issue with presigned_url_artifact requests being in the wrong format (#​13366, @​WeichenXu123)
  • [Models] Update Databricks dependency extraction functionality to work with the langchain-databricks partner package. (#​13266, @​B-Step62)
  • [Model Registry] Fix retry and credential refresh issues with artifact downloads from the model registry (#​12935, @​rohitarun-db)
  • [Tracking] Fix LangChain autologging so that langchain-community is not required for partner packages (#​13172, @​B-Step62)
  • [Artifacts] Fix issues with file removal for the local artifact repository (#​13005, @​rzalawad)

Documentation updates:

Small bug fixes and documentation updates:

#​13372, #​13271, #​13243, #​13226, #​13190, #​13230, #​13208, #​13130, #​13045, #​13094, @​B-Step62; #​13302, #​13238, #​13234, #​13205, #​13200, #​13196, #​13198, #​13193, #​13192, #​13194, #​13189, #​13184, #​13182, #​13161, #​13179, #​13178, #​13110, #​13162, #​13173, #​13171, #​13169, #​13168, #​13167, #​13156, #​13127, #​13133, #​13089, #​13073, #​13057, #​13058, #​13067, #​13062, #​13061, #​13052, @​harupy; #​13295, #​13219, #​13038, @​serena-ruan; #​13176, #​13164, @​WeichenXu123; #​13163, @​gabrielfu; #​13186, @​varshinimuthukumar1; #​13128, #​13115, @​nojaf; #​13120, @​levscaut; #​13152, #​13075, @​BenWilson2; #​13138, @​tanguylefloch-veesion; #​13087, [@​S


Configuration

📅 Schedule: Branch creation - "on the 2nd and 4th day instance on sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate-mlflow-2.x branch 2 times, most recently from 8bc6235 to 0bf5c90 Compare September 13, 2024 22:02
@renovate renovate bot changed the title chore(deps): update dependency mlflow to v2.16.0 chore(deps): update dependency mlflow to v2.16.1 Sep 13, 2024
@renovate renovate bot changed the title chore(deps): update dependency mlflow to v2.16.1 chore(deps): update dependency mlflow to v2.16.2 Sep 17, 2024
@renovate renovate bot force-pushed the renovate-mlflow-2.x branch 4 times, most recently from 8bfa40b to 46678b5 Compare September 18, 2024 12:44
@renovate renovate bot force-pushed the renovate-mlflow-2.x branch 2 times, most recently from a77d294 to 6111269 Compare September 30, 2024 11:38
@renovate renovate bot force-pushed the renovate-mlflow-2.x branch from 6111269 to 6922717 Compare October 3, 2024 09:54
@renovate renovate bot force-pushed the renovate-mlflow-2.x branch from 6922717 to 7112957 Compare October 12, 2024 04:04
@renovate renovate bot changed the title chore(deps): update dependency mlflow to v2.16.2 chore(deps): update dependency mlflow to v2.17.0 Oct 12, 2024
@renovate renovate bot force-pushed the renovate-mlflow-2.x branch from 7112957 to cb4f961 Compare October 25, 2024 11:03
@renovate renovate bot changed the title chore(deps): update dependency mlflow to v2.17.0 chore(deps): update dependency mlflow to v2.17.1 Oct 25, 2024
@renovate renovate bot force-pushed the renovate-mlflow-2.x branch from cb4f961 to e5f57bf Compare October 31, 2024 10:36
@renovate renovate bot changed the title chore(deps): update dependency mlflow to v2.17.1 chore(deps): update dependency mlflow to v2.17.2 Oct 31, 2024
@renovate renovate bot force-pushed the renovate-mlflow-2.x branch from e5f57bf to 06ecc3c Compare November 18, 2024 17:20
@renovate renovate bot changed the title chore(deps): update dependency mlflow to v2.17.2 chore(deps): update dependency mlflow to v2.18.0 Nov 18, 2024
Copy link
Contributor Author

renovate bot commented Nov 18, 2024

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: tests/notebooks/cpu/mlflow/requirements.txt
Command failed: pip-compile requirements.in
  ERROR: Ignored the following yanked versions: 2.0.0, 2.12.0
  ERROR: Ignored the following versions that require a different python version: 2.18.0 Requires-Python >=3.9; 2.18.0rc0 Requires-Python >=3.9; 2.19.0 Requires-Python >=3.9; 2.19.0rc0 Requires-Python >=3.9; 7.2.11 Requires-Python >=3.9; 7.2.12 Requires-Python >=3.9
  ERROR: Could not find a version that satisfies the requirement mlflow==2.19.0 (from versions: 0.0.1, 0.1.0, 0.2.0, 0.2.1, 0.3.0, 0.4.0, 0.4.1, 0.4.2, 0.5.0, 0.5.1, 0.5.2, 0.6.0, 0.7.0, 0.8.0, 0.8.1, 0.8.2, 0.9.0, 0.9.0.1, 0.9.1, 1.0.0, 1.1.0, 1.1.1.dev0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.7.1, 1.7.2, 1.8.0, 1.9.0, 1.9.1, 1.10.0, 1.11.0, 1.12.0, 1.12.1, 1.13, 1.13.1, 1.14.0, 1.14.1, 1.15.0, 1.16.0, 1.17.0, 1.18.0, 1.19.0, 1.20.0, 1.20.1, 1.20.2, 1.21.0, 1.22.0, 1.23.0, 1.23.1, 1.24.0, 1.25.0, 1.25.1, 1.26.0, 1.26.1, 1.27.0, 1.28.0, 1.29.0, 1.30.0, 1.30.1, 2.0.0rc0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.3.2, 2.4.0, 2.4.1, 2.4.2, 2.5.0, 2.6.0, 2.7.0, 2.7.1, 2.8.0, 2.8.1, 2.9.0, 2.9.1, 2.9.2, 2.10.0, 2.10.1, 2.10.2, 2.11.0, 2.11.1, 2.11.2, 2.11.3, 2.11.4, 2.12.1, 2.12.2, 2.13.0, 2.13.1, 2.13.2, 2.14.0rc0, 2.14.0, 2.14.1, 2.14.2.dev0, 2.14.2, 2.14.3, 2.15.0rc0, 2.15.0, 2.15.1, 2.16.0, 2.16.1, 2.16.2, 2.17.0rc0, 2.17.0, 2.17.1, 2.17.2)
Traceback (most recent call last):
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 397, in resolve
    self._add_to_criteria(self.state.criteria, r, parent=None)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 174, in _add_to_criteria
    raise RequirementsConflicted(criterion)
pip._vendor.resolvelib.resolvers.RequirementsConflicted: Requirements conflict: SpecifierRequirement('mlflow==2.19.0')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 95, in resolve
    result = self._result = resolver.resolve(
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 546, in resolve
    state = resolution.resolve(requirements, max_rounds=max_rounds)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 399, in resolve
    raise ResolutionImpossible(e.criterion.information)
pip._vendor.resolvelib.resolvers.ResolutionImpossible: [RequirementInformation(requirement=SpecifierRequirement('mlflow==2.19.0'), parent=None)]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/bin/pip-compile", line 8, in <module>
    sys.exit(cli())
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/decorators.py", line 33, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/piptools/scripts/compile.py", line 470, in cli
    results = resolver.resolve(max_rounds=max_rounds)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/piptools/resolver.py", line 604, in resolve
    is_resolved = self._do_resolve(
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/piptools/resolver.py", line 636, in _do_resolve
    resolver.resolve(
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 104, in resolve
    raise error from e
pip._internal.exceptions.DistributionNotFound: No matching distribution found for mlflow==2.19.0

File name: tests/notebooks/cpu/mlflow-kserve/requirements.txt
Command failed: pip-compile requirements.in
  ERROR: Ignored the following yanked versions: 2.0.0, 2.12.0
  ERROR: Ignored the following versions that require a different python version: 2.18.0 Requires-Python >=3.9; 2.18.0rc0 Requires-Python >=3.9; 2.19.0 Requires-Python >=3.9; 2.19.0rc0 Requires-Python >=3.9; 7.2.11 Requires-Python >=3.9; 7.2.12 Requires-Python >=3.9
  ERROR: Could not find a version that satisfies the requirement mlflow==2.19.0 (from versions: 0.0.1, 0.1.0, 0.2.0, 0.2.1, 0.3.0, 0.4.0, 0.4.1, 0.4.2, 0.5.0, 0.5.1, 0.5.2, 0.6.0, 0.7.0, 0.8.0, 0.8.1, 0.8.2, 0.9.0, 0.9.0.1, 0.9.1, 1.0.0, 1.1.0, 1.1.1.dev0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.7.1, 1.7.2, 1.8.0, 1.9.0, 1.9.1, 1.10.0, 1.11.0, 1.12.0, 1.12.1, 1.13, 1.13.1, 1.14.0, 1.14.1, 1.15.0, 1.16.0, 1.17.0, 1.18.0, 1.19.0, 1.20.0, 1.20.1, 1.20.2, 1.21.0, 1.22.0, 1.23.0, 1.23.1, 1.24.0, 1.25.0, 1.25.1, 1.26.0, 1.26.1, 1.27.0, 1.28.0, 1.29.0, 1.30.0, 1.30.1, 2.0.0rc0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.3.2, 2.4.0, 2.4.1, 2.4.2, 2.5.0, 2.6.0, 2.7.0, 2.7.1, 2.8.0, 2.8.1, 2.9.0, 2.9.1, 2.9.2, 2.10.0, 2.10.1, 2.10.2, 2.11.0, 2.11.1, 2.11.2, 2.11.3, 2.11.4, 2.12.1, 2.12.2, 2.13.0, 2.13.1, 2.13.2, 2.14.0rc0, 2.14.0, 2.14.1, 2.14.2.dev0, 2.14.2, 2.14.3, 2.15.0rc0, 2.15.0, 2.15.1, 2.16.0, 2.16.1, 2.16.2, 2.17.0rc0, 2.17.0, 2.17.1, 2.17.2)
Traceback (most recent call last):
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 397, in resolve
    self._add_to_criteria(self.state.criteria, r, parent=None)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 174, in _add_to_criteria
    raise RequirementsConflicted(criterion)
pip._vendor.resolvelib.resolvers.RequirementsConflicted: Requirements conflict: SpecifierRequirement('mlflow==2.19.0')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 95, in resolve
    result = self._result = resolver.resolve(
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 546, in resolve
    state = resolution.resolve(requirements, max_rounds=max_rounds)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 399, in resolve
    raise ResolutionImpossible(e.criterion.information)
pip._vendor.resolvelib.resolvers.ResolutionImpossible: [RequirementInformation(requirement=SpecifierRequirement('mlflow==2.19.0'), parent=None)]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/bin/pip-compile", line 8, in <module>
    sys.exit(cli())
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/decorators.py", line 33, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/piptools/scripts/compile.py", line 470, in cli
    results = resolver.resolve(max_rounds=max_rounds)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/piptools/resolver.py", line 604, in resolve
    is_resolved = self._do_resolve(
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/piptools/resolver.py", line 636, in _do_resolve
    resolver.resolve(
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 104, in resolve
    raise error from e
pip._internal.exceptions.DistributionNotFound: No matching distribution found for mlflow==2.19.0

File name: tests/notebooks/cpu/e2e-wine/requirements.txt
Command failed: pip-compile requirements.in
  ERROR: Ignored the following yanked versions: 2.0.0, 2.12.0
  ERROR: Ignored the following versions that require a different python version: 2.10.0 Requires-Python <3.13.0,>=3.9.0; 2.10.1 Requires-Python >=3.9.0; 2.11.0 Requires-Python >=3.9.0; 2.18.0 Requires-Python >=3.9; 2.18.0rc0 Requires-Python >=3.9; 2.19.0 Requires-Python >=3.9; 2.19.0rc0 Requires-Python >=3.9; 7.2.11 Requires-Python >=3.9; 7.2.12 Requires-Python >=3.9
  ERROR: Could not find a version that satisfies the requirement mlflow==2.19.0 (from versions: 0.0.1, 0.1.0, 0.2.0, 0.2.1, 0.3.0, 0.4.0, 0.4.1, 0.4.2, 0.5.0, 0.5.1, 0.5.2, 0.6.0, 0.7.0, 0.8.0, 0.8.1, 0.8.2, 0.9.0, 0.9.0.1, 0.9.1, 1.0.0, 1.1.0, 1.1.1.dev0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.7.1, 1.7.2, 1.8.0, 1.9.0, 1.9.1, 1.10.0, 1.11.0, 1.12.0, 1.12.1, 1.13, 1.13.1, 1.14.0, 1.14.1, 1.15.0, 1.16.0, 1.17.0, 1.18.0, 1.19.0, 1.20.0, 1.20.1, 1.20.2, 1.21.0, 1.22.0, 1.23.0, 1.23.1, 1.24.0, 1.25.0, 1.25.1, 1.26.0, 1.26.1, 1.27.0, 1.28.0, 1.29.0, 1.30.0, 1.30.1, 2.0.0rc0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.3.2, 2.4.0, 2.4.1, 2.4.2, 2.5.0, 2.6.0, 2.7.0, 2.7.1, 2.8.0, 2.8.1, 2.9.0, 2.9.1, 2.9.2, 2.10.0, 2.10.1, 2.10.2, 2.11.0, 2.11.1, 2.11.2, 2.11.3, 2.11.4, 2.12.1, 2.12.2, 2.13.0, 2.13.1, 2.13.2, 2.14.0rc0, 2.14.0, 2.14.1, 2.14.2.dev0, 2.14.2, 2.14.3, 2.15.0rc0, 2.15.0, 2.15.1, 2.16.0, 2.16.1, 2.16.2, 2.17.0rc0, 2.17.0, 2.17.1, 2.17.2)
Traceback (most recent call last):
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 397, in resolve
    self._add_to_criteria(self.state.criteria, r, parent=None)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 174, in _add_to_criteria
    raise RequirementsConflicted(criterion)
pip._vendor.resolvelib.resolvers.RequirementsConflicted: Requirements conflict: SpecifierRequirement('mlflow==2.19.0')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 95, in resolve
    result = self._result = resolver.resolve(
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 546, in resolve
    state = resolution.resolve(requirements, max_rounds=max_rounds)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 399, in resolve
    raise ResolutionImpossible(e.criterion.information)
pip._vendor.resolvelib.resolvers.ResolutionImpossible: [RequirementInformation(requirement=SpecifierRequirement('mlflow==2.19.0'), parent=None)]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/bin/pip-compile", line 8, in <module>
    sys.exit(cli())
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/click/decorators.py", line 33, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/piptools/scripts/compile.py", line 470, in cli
    results = resolver.resolve(max_rounds=max_rounds)
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/piptools/resolver.py", line 604, in resolve
    is_resolved = self._do_resolve(
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/piptools/resolver.py", line 636, in _do_resolve
    resolver.resolve(
  File "/opt/containerbase/tools/pip-tools/7.4.1/3.8.10/lib/python3.8/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 104, in resolve
    raise error from e
pip._internal.exceptions.DistributionNotFound: No matching distribution found for mlflow==2.19.0

@renovate renovate bot force-pushed the renovate-mlflow-2.x branch 3 times, most recently from bc09d03 to df28f87 Compare December 3, 2024 08:04
@renovate renovate bot force-pushed the renovate-mlflow-2.x branch from df28f87 to ba5dd1b Compare December 11, 2024 12:07
@renovate renovate bot changed the title chore(deps): update dependency mlflow to v2.18.0 chore(deps): update dependency mlflow to v2.19.0 Dec 11, 2024
@renovate renovate bot force-pushed the renovate-mlflow-2.x branch from ba5dd1b to aa5f6c2 Compare December 12, 2024 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants