From 44a72ef9b8975ff650717a41a342b2008936f400 Mon Sep 17 00:00:00 2001 From: "Ricardo M. Oliveira" Date: Mon, 25 Nov 2024 11:25:54 -0300 Subject: [PATCH] Adds the component_metadata.yaml to track KFP releases across DSP ones Signed-off-by: Ricardo M. Oliveira --- config/component_metadata.yaml | 4 ++++ docs/release/RELEASE.md | 11 ++++++----- 2 files changed, 10 insertions(+), 5 deletions(-) create mode 100644 config/component_metadata.yaml diff --git a/config/component_metadata.yaml b/config/component_metadata.yaml new file mode 100644 index 000000000..f553b6a33 --- /dev/null +++ b/config/component_metadata.yaml @@ -0,0 +1,4 @@ +releases: + - name: Kubeflow Pipelines + version: 2.2.0 + repoUrl: https://github.com/kubeflow/pipelines diff --git a/docs/release/RELEASE.md b/docs/release/RELEASE.md index 56c5cc8ad..dc34b8020 100644 --- a/docs/release/RELEASE.md +++ b/docs/release/RELEASE.md @@ -38,15 +38,16 @@ Steps on how to release `x.y+1` 1. Ensure `compatibility.yaml` is upto date, and generate a new `compatibility.md` - Use [release-tools] to accomplish this -2. Cut branch `vx.y+1` from `main/master` +2. If the changes include a code rebase from KFP repo, ensure `config/component_metadata.yaml` is updated with the respective KFP version +3. Cut branch `vx.y+1` from `main/master` - Do this for DSPO and DSP repos -3. Build images. Use the [build-tags] workflow, specifying the branches from above -4. Retrieve the sha images from the resulting workflow (check quay.io for the digests) +4. Build images. Use the [build-tags] workflow, specifying the branches from above +5. Retrieve the sha images from the resulting workflow (check quay.io for the digests) - Using [release-tools] generate a `params.env` and submit a new pr to `vx.y+1` branch - For images pulled from registry, ensure latest images are upto date -5. Perform any tests on the branch, confirm stability +6. Perform any tests on the branch, confirm stability - If issues are found, they should be corrected in `main/master` and be cherry-picked into this branch. -6. Create a tag release (using the branches from above) for `x.y+1.0` in DSPO and DSP (e.g. `v1.3.0`) +7. Create a tag release (using the branches from above) for `x.y+1.0` in DSPO and DSP (e.g. `v1.3.0`) ## PATCH Releases