Skip to content

chore: update release instructions#12117

Merged
google-oss-prow[bot] merged 1 commit intokubeflow:masterfrom
HumairAK:release-notes-update
Aug 7, 2025
Merged

chore: update release instructions#12117
google-oss-prow[bot] merged 1 commit intokubeflow:masterfrom
HumairAK:release-notes-update

Conversation

@HumairAK
Copy link
Collaborator

@HumairAK HumairAK commented Aug 6, 2025

Description of your changes:

Update release instructions, update kfp sdk release method to match the other python packages via makefile. Also add readthedocs instructions.

The instructions make using a release-branch a requirement, we will no longer be releasing from master.

Checklist:

@google-oss-prow google-oss-prow bot requested review from hbelmiro and zazulam August 6, 2025 16:05
@HumairAK HumairAK requested review from droctothorpe and removed request for hbelmiro August 6, 2025 16:05
@HumairAK HumairAK force-pushed the release-notes-update branch 2 times, most recently from c037a8b to 8da5983 Compare August 6, 2025 16:09
@HumairAK HumairAK requested a review from mprahl August 7, 2025 12:07
@HumairAK
Copy link
Collaborator Author

HumairAK commented Aug 7, 2025

We also have situations where one package depends on another, the dependency goes:

  • pipeline-api-spec
    • depended on by kfp-sdk & kfp-kubernetes
  • kfp-sdk
    • depended on by kfp-kubernetes
  • kfp-server-api
    • depended on by kfp-sdk

We also have tests that reference these packages. So I think whenever we bump any of the packages that have dependents, we should bump in the all respective requirements.in and requirements.txt across the repo. Thoughts?

Some automated tooling here would be nice as well. I'm thinking we want to avoid scenarios like this: #12120

Copy link
Member

@chensun chensun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Thanks!

Signed-off-by: Humair Khan <HumairAK@users.noreply.github.com>
@HumairAK HumairAK force-pushed the release-notes-update branch from 8da5983 to 614f6a4 Compare August 7, 2025 18:28
@google-oss-prow google-oss-prow bot removed the lgtm label Aug 7, 2025
Copy link
Collaborator

@mprahl mprahl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mprahl

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-prow google-oss-prow bot merged commit 6bf566d into kubeflow:master Aug 7, 2025
23 checks passed
HumairAK added a commit to HumairAK/data-science-pipelines that referenced this pull request Aug 7, 2025
Signed-off-by: Humair Khan <HumairAK@users.noreply.github.com>
google-oss-prow bot pushed a commit that referenced this pull request Aug 7, 2025
* update kfp server api for kfp sdk (#12120)

with the recent proto change the kfp server no long accepts body as an
acceptable parameter, due to this breaking change the min kfp-server-api
in kfp sdk needs to be bumped and a new kfp sdk needs to be released.

Signed-off-by: Humair Khan <HumairAK@users.noreply.github.com>

* chore: update release instructions (#12117)

Signed-off-by: Humair Khan <HumairAK@users.noreply.github.com>

---------

Signed-off-by: Humair Khan <HumairAK@users.noreply.github.com>
kaikaila pushed a commit to kaikaila/kubeflow-pipelines that referenced this pull request Aug 7, 2025
Signed-off-by: Humair Khan <HumairAK@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants