Migrate vercel integration to otel and update doc #18784
Merged
B-Step62 merged 15 commits intomlflow:masterfrom Dec 2, 2025
Merged
Migrate vercel integration to otel and update doc #18784B-Step62 merged 15 commits intomlflow:masterfrom
B-Step62 merged 15 commits intomlflow:masterfrom
Conversation
This was referenced Nov 11, 2025
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>
b0a8219 to
cb878ec
Compare
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>
daniellok-db
reviewed
Dec 1, 2025
daniellok-db
reviewed
Dec 1, 2025
| @@ -1,15 +1,8 @@ | |||
| { | |||
| "extends": "../../tsconfig.base.json", | |||
Collaborator
There was a problem hiding this comment.
wait does this file exist? i don't see it
Collaborator
Author
There was a problem hiding this comment.
I forgot to commit the file, thanks for the catch:)
daniellok-db
reviewed
Dec 1, 2025
Collaborator
There was a problem hiding this comment.
is it possible to add some deprecation notice to the NPM page?
Collaborator
Author
There was a problem hiding this comment.
Sure, I will publish a new version with the updated README once the doc is released.
daniellok-db
approved these changes
Dec 1, 2025
Collaborator
daniellok-db
left a comment
There was a problem hiding this comment.
LGTM since it's mainly a doc change. looks like there may be some rebase errors to resolve though
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>
Contributor
|
Documentation preview for bf890d9 is available at: Changed Pages (1)
More info
|
Collaborator
Author
|
All failed tests are due to connection error when loading dependencies in model logging tests, not related to this PR. Force merging. |
BenWilson2
pushed a commit
to BenWilson2/mlflow
that referenced
this pull request
Dec 4, 2025
Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>
BenWilson2
pushed a commit
that referenced
this pull request
Dec 4, 2025
Signed-off-by: B-Step62 <yuki.watanabe@databricks.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.
🥞 Stacked PR
Use this link to review incremental changes.
What changes are proposed in this pull request?
Remove the in-house vercel AI integration and update the doc to use otel.
This let us using ESM for module system, not commonjs.
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow 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" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
Yesshould be selected for bug fixes, documentation updates, and other small changes.Noshould be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.What is a minor/patch release?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.