Update branch references in kubeflow repo based the new release (#583)

Author: atheo89

.github/scripts/create-release.sh

@@ -26,8 +26,8 @@ set -euo pipefail
 #   recent commit will be used.
 #       git branch -r returns branches in the form of <remote>/<branch>
 #            examples: 
-#               origin/v1.9-branch  : match
-#               origin/main         : no match    
+#               origin/v1.10-branch  : match
+#               origin/main          : no match    
 #     
 # Arguments: 
 #   $1 : Release branch to use if provided.
@@ -72,7 +72,7 @@ _get_latest_release_tag()
 #   This determination is critical in being able to properly auto-increment the release name. See comments on _get_target_release_json() for further details.
 #
 # Arguments: 
-#   $1 : Branch prefix that is being used to create the new release.  kubeflow names branches like 'v1.9-branch'.  The branch prefix would then be expected to be 'v1.9'
+#   $1 : Branch prefix that is being used to create the new release.  kubeflow names branches like 'v1.10-branch'.  The branch prefix would then be expected to be 'v1.10'
 #   $2 : Tag name corresponding to the most recent published release
 #
 # Returns:
@@ -103,13 +103,13 @@ _same_branch_as_prior_release()
 #   If a release name is provided in the arguments, it is used as-is without any further computation.  However, if a release name is not provided, this function will
 #   analyze the state of the release branch as well as the most recent published release tag, to determine the appropriate auto-incrementing strategy. Consider the 
 #   following scenarios:
-#       _get_target_release_json "v1.9-branch" ""
+#       _get_target_release_json "v1.10-branch" ""
 #           In this case, the most recent published release is retrieved, and, based on _same_branch_as_prior_release():
-#               - if the most recent published release is associated with the release branch, the {release} segment of the name is incremented by 1 (ex: v1.9.0-5 to v1.9.0-6)
-#               - if the most recent published release is not associated with the release branch, release name is "reset" based on the branch (ex: v1.9.0-1)
+#               - if the most recent published release is associated with the release branch, the {release} segment of the name is incremented by 1 (ex: v1.10.0-5 to v1.10.0-6)
+#               - if the most recent published release is not associated with the release branch, release name is "reset" based on the branch (ex: v1.10.0-1)
 #
-#       _get_target_release_json "v1.9-branch" "v1.9.0-5"
-#            In this case, the release name is simply the provided 'v1.9.0-5' argument.  If this release already exists, the script will subsequently error.
+#       _get_target_release_json "v1.10-branch" "v1.10.0-5"
+#            In this case, the release name is simply the provided 'v1.10.0-5' argument.  If this release already exists, the script will subsequently error.
 #
 #   Generally speaking, it should not be necessary to provide the $2 argument unless under extraordinary circumstances.
 #

.github/workflows/code-quality.yaml

@@ -5,7 +5,7 @@ name: Code static analysis
   pull_request:
     branches:
       - main
-      - v1.9-branch
+      - v1.10-branch
   workflow_dispatch:
 
 permissions:

.github/workflows/kubeflow-release.yaml

@@ -15,15 +15,15 @@ env:
   CREATE_NEW_RELEASE: ${{ inputs.release-type == 'Release' }}
   REPO_OWNER: opendatahub-io
   REPO_NAME: kubeflow
-  BRANCH_NAME: v1.9-branch
+  BRANCH_NAME: v1.10-branch
 
 jobs:
-  # 1. Sync changes to opendatahub:v1.9-branch from opendatahub:main
+  # 1. Sync changes to opendatahub:v1.10-branch from opendatahub:main
   sync-main-to-release-branch:
     uses: opendatahub-io/kubeflow/.github/workflows/sync-branches.yaml@main
     with:
       source: "main"
-      target: "v1.9-branch"
+      target: "v1.10-branch"
 
   # 2. Poll for images to be available on quay.io the readiness of the images usually takes ~10 mins
   wait-images-are-ready-on-quay:
@@ -46,8 +46,8 @@ jobs:
 
           # Images to check
           IMAGES=(
-            "quay.io/opendatahub/kubeflow-notebook-controller:1.9-${GIT_HASH}"
-            "quay.io/opendatahub/odh-notebook-controller:1.9-${GIT_HASH}"
+            "quay.io/opendatahub/kubeflow-notebook-controller:1.10-${GIT_HASH}"
+            "quay.io/opendatahub/odh-notebook-controller:1.10-${GIT_HASH}"
           )
 
           # Sleep for 5 minutes before starting polling
@@ -84,7 +84,7 @@ jobs:
     if: ${{ needs.wait-images-are-ready-on-quay.outputs.images_ready == 'true' }}
     uses: opendatahub-io/kubeflow/.github/workflows/notebook-controller-images-updater.yaml@main
     with:
-      branch-name: "v1.9-branch"
+      branch-name: "v1.10-branch"
       organization: "opendatahub-io"
       generate-pr: "true"
     secrets:
@@ -146,4 +146,4 @@ jobs:
     if: ${{ needs.check-pr-merged.outputs.pr_merged == 'true' && inputs.release-type == 'Release' }}
     uses: opendatahub-io/kubeflow/.github/workflows/create-release.yaml@main
     with:
-      target_branch: "v1.9-branch"
+      target_branch: "v1.10-branch"

.github/workflows/notebook_controller_integration_test.yaml

@@ -4,7 +4,7 @@ on:
   pull_request:
     branches:
       - main
-      - v1.9-branch
+      - v1.10-branch
     paths:
       - .github/workflows/notebook_controller_integration_test.yaml
       - components/notebook-controller/**

.github/workflows/notebook_controller_unit_test.yaml

@@ -4,7 +4,7 @@ on:
   pull_request:
     branches:
       - main
-      - v1.9-branch
+      - v1.10-branch
     paths:
       - .github/workflows/notebook_controller_unit_test.yaml
       - components/notebook-controller/**

.github/workflows/odh_notebook_controller_integration_test.yaml

@@ -4,7 +4,7 @@ on:
   pull_request:
     branches:
       - main
-      - v1.9-branch
+      - v1.10-branch
     paths:
       - .github/workflows/odh_notebook_controller_integration_test.yaml
       - components/notebook-controller/**

.github/workflows/odh_notebook_controller_unit_test.yaml

@@ -4,7 +4,7 @@ on:
   pull_request:
     branches:
       - main
-      - v1.9-branch
+      - v1.10-branch
     paths:
       - .github/workflows/odh_notebook_controller_unit_test.yaml
       - components/odh-notebook-controller/**

components/notebook-controller/generate-metadata-yaml.sh

@@ -44,7 +44,7 @@
 ##                  - version attribute of 'releases' element at index 0
 ##                  - defaults to a value derived from contents of ./releasing/version/VERSION
 ##                      - 1st line of VERSION is read, and any leading 'v' character is removed from content
-##                        - ex: v1.9.0 -> 1.9.0
+##                        - ex: v1.10.0 -> 1.10.0
 ##              - [optional] -r <repoUrl>
 ##                  - repoUrl attribute of 'releases' element at index 0
 ##                  - defaults to a value derived from the 'repo' attribute of ./components/notebook-controller/PROJECT