Add Modernizing Kubeflow Pipelines UI blog post#196
Add Modernizing Kubeflow Pipelines UI blog post#196google-oss-prow[bot] merged 6 commits intokubeflow:masterfrom
Conversation
Signed-off-by: manaswinidas <dasmanaswini10@gmail.com>
Co-authored-by: Julius von Kohout <45896133+juliusvonkohout@users.noreply.github.com> Signed-off-by: Manaswini Das <dasmanaswini10@gmail.com>
Co-authored-by: Julius von Kohout <45896133+juliusvonkohout@users.noreply.github.com> Signed-off-by: Manaswini Das <dasmanaswini10@gmail.com>
Co-authored-by: Julius von Kohout <45896133+juliusvonkohout@users.noreply.github.com> Signed-off-by: Manaswini Das <dasmanaswini10@gmail.com>
Co-authored-by: Julius von Kohout <45896133+juliusvonkohout@users.noreply.github.com> Signed-off-by: Manaswini Das <dasmanaswini10@gmail.com>
Co-authored-by: Julius von Kohout <45896133+juliusvonkohout@users.noreply.github.com> Signed-off-by: Manaswini Das <dasmanaswini10@gmail.com>
|
@juliusvonkohout accepted all your suggestions |
|
@juliusvonkohout can you give an LGTM and what's the publication process ? Do I need LGTM from any other stakeholders ? |
Yes, lgtms from KFP maintainers except myself. |
|
@droctothorpe @mprahl can I get a LGTM from you folks to publish this post? thanks in advance. |
|
cc @zazulam @james-jwu @chensun Can I get a LGTM from you folks to publish this post? They need LGTM from KFP approvers. Thanks in advance. |
|
/lgtm Excellent blog post! It's good to see such great work highlighted. Kudos to everyone involved! |
|
@juliusvonkohout Is this good to merge ? |
|
@andreyvelich @franciscojavierarceo can I get an LGTM/approval on this ? |
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: juliusvonkohout The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This blog post covers the Kubeflow Pipelines frontend modernization from React 16 to React 19, including the deps-first upgrade strategy, toolchain replacements (CRA → Vite, Jest → Vitest, Material-UI v3 → MUI v5), and the impact on users and contributors.
For the full execution plan and PR dependency graph, see the react-18-19-upgrade-checklist.md.