release(main): v0.17.0

.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.16.0"
+  ".": "0.17.0"
 }

CHANGELOG.md

@@ -1,5 +1,20 @@
 # Changelog
 
+## 0.17.0 (2024-09-27)
+
+<!-- Release notes generated using configuration in .github/release.yaml at main -->
+
+## What's Changed
+### Exciting New Features 🎉
+* feat: Support XValidations (CEL) for CC variables by @jimmidyson in https://github.com/nutanix-cloud-native/cluster-api-runtime-extensions-nutanix/pull/916
+* feat: Update addon versions by @jimmidyson in https://github.com/nutanix-cloud-native/cluster-api-runtime-extensions-nutanix/pull/917
+### Other Changes
+* build: Fix up metadata missed in v0.16.0 release process by @jimmidyson in https://github.com/nutanix-cloud-native/cluster-api-runtime-extensions-nutanix/pull/920
+* build: Consistently format even generated files by @jimmidyson in https://github.com/nutanix-cloud-native/cluster-api-runtime-extensions-nutanix/pull/923
+
+
+**Full Changelog**: https://github.com/nutanix-cloud-native/cluster-api-runtime-extensions-nutanix/compare/v0.16.0...v0.17.0
+
 ## 0.16.0 (2024-09-25)
 
 <!-- Release notes generated using configuration in .github/release.yaml at main -->

docs/content/contributing/releasing.md

@@ -45,9 +45,11 @@ for e.g. local development and e2e tests:
 1. Add the new release to the e2e configuration `test/e2e/data/shared/v1beta1-caren/metadata.yaml` release series.
 1. Add the next release to the e2e configuration `test/e2e/data/shared/v1beta1-caren/metadata.yaml` (e.g. if release
    `v0.6.0` then add release series for `v0.7`).
-1. Update the `caren` provider configuration in `test/e2e/config/caren.yaml` with the new release (replacing the last
-   minor release with the new minor release version) and the next minor release configuration (replacing the `v0.x.99`
-   configuration).
+1. Update the `caren` provider configuration in `test/e2e/config/caren.yaml`:
+   - The first reference should be the most recent successful patch release of the previous minor version. For example,
+     if you releasing v0.22, reference the most recent successful patch release of v0.21.
+   - The second reference should be the 99th patch version of the minor version being released. For example, if you
+     are releasing v0.22, the reference should be v0.22.99.
 1. Commit the changed files:
 
    ```shell

docs/hugo.toml

@@ -71,7 +71,7 @@ archived_version = false
 # The version number for the version of the docs represented in this doc set.
 # Used in the "version-banner" partial to display a version number for the
 # current doc set.
-version = "0.16.0"
+version = "0.17.0"
 
 # A link to latest version of the docs. Used in the "version-banner" partial to
 # point people to the main doc site.

metadata.yaml

@@ -49,3 +49,6 @@ releaseSeries:
   - contract: v1beta1
     major: 0
     minor: 16
+  - contract: v1beta1
+    major: 0
+    minor: 17

test/e2e/config/caren.yaml

@@ -134,6 +134,8 @@ providers:
 - name: caren
   type: RuntimeExtensionProvider
   versions:
+  # Upgrade e2e tests will use this as the "upgrade from" version.
+  # This should reference the most recent successful release.
   - name: "{go://github.com/nutanix-cloud-native/[email protected]}"
     value: "https://github.com/nutanix-cloud-native/cluster-api-runtime-extensions-nutanix/releases/download/{go://github.com/nutanix-cloud-native/[email protected]}/runtime-extension-components.yaml"
     type: "url"
@@ -145,7 +147,7 @@ providers:
       new: "--v=8"
     - old: --metrics-addr=127.0.0.1:8080
       new: --metrics-addr=:8080
-  - name: v0.17.99 # "vNext"; use manifests from local source files
+  - name: v0.18.99 # "vNext"; use manifests from local source files
     value: "file://../../../runtime-extension-components.yaml"
     type: "url"
     contract: v1beta1

test/e2e/data/shared/v1beta1-caren/metadata.yaml

@@ -40,3 +40,6 @@ releaseSeries:
   - contract: v1beta1
     major: 0
     minor: 17
+  - contract: v1beta1
+    major: 0
+    minor: 18