[NeriCarcasci]

Related Issues/PRs

Relates to CI noise on midstream CVE PRs such as #663 and #656 (failures are pre-existing on rhoai-3.3, not caused by those CVE diffs)

What changes are proposed in this pull request?

Pin three unpinned CI/test/docs dependencies that recently broke rhoai-3.3 PR checks via version mismatch, and make docs CI pick up requirement-file changes:

• pyspark<4.1.0 in requirements/test-requirements.txt, requirements/extra-ml-requirements.txt, and requirements/doc-requirements.txt (matches rhoai-3.4 / upstream). Unpinned pyspark==4.2.0 breaks genai Spark fixtures when empty expectations: {} become {expected_response: null}.
• haystack-ai>=2.0.0,<3 in requirements/doc-requirements.txt and requirements/extra-ml-requirements.txt. haystack-ai==3.0.0 removed OpenTelemetryTracer, which mlflow.haystack.autolog still imports.
• ag2>=0.7.0,<1 in requirements/extra-ml-requirements.txt. ag2==1.0.0 renamed the import path from autogen to ag2, breaking flavors collection (import autogen).
• Add requirements/** to .github/workflows/docs.yml path filters so docs/build CI runs when these pins change.

How is this PR tested?

• Existing unit/integration tests
• New unit/integration tests
• Manual tests

• Resolved pins in a clean venv: pyspark==4.0.4, ag2==0.14.0, haystack-ai==2.31.0
• Verified import autogen works under ag2<1
• Verified from haystack.tracing import OpenTelemetryTracer and mlflow.haystack.autolog import under haystack-ai<3
• Confirmed upper bounds reject the known-breaking majors (4.2.0 / 1.0.0 / 3.0.0)

Does this PR require documentation update?

• No.
• Yes. I've updated:
  • Examples
  • API references
  • Instructions

Does this PR require updating the MLflow Skills repository?

• No.
• Yes. Please link the corresponding PR or explain how you plan to update it.

Release Notes

Is this a user-facing change?

• No.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/tracking: Tracking Service, tracking client APIs, autologging
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
• area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
• area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
• area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
• area/projects: MLproject format, project running backends
• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/build: Build and test infrastructure for MLflow
• area/docs: MLflow documentation pages

How should the PR be classified in the release notes? Choose one:

• rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

Is this PR a critical bug fix or security fix that should go into the next patch release?

What is a minor/patch release?

• Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
  Minor releases are expected to contain larger changes, such as new features and improvements. Non-critical bug fixes and doc updates can be included as well. By default, your PR should target the next minor release.
• Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
  Patch releases are typically only performed when there has been a major regression or bug in the latest release. For the sake of stability, your PR should not be included in a patch release unless it is a critical fix, or if the risk level of your PR is exceedingly low.

• This PR is critical and needs to be in the next patch release
• This PR can wait for the next minor release

Made with Cursor

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

[kramaranya]

/lgtm
/approve