Release 0.16 (#544)

* docs: Update TimeSeries LLM Forecast API title and add to sidebar

Signed-off-by: Sivanantham Chinnaiyan <[email protected]>

* docs: Update links for Batch InferenceService and Canary Deployments in predictive-first-isvc.md; remove TODO comments
fix: Update ActiveDocsVersion to return latest version label instead of hardcoded value

Signed-off-by: Sivanantham Chinnaiyan <[email protected]>

* docs: Update CRD documentation generation to use RELEASE_VERSION; modify release script to set environment variable and address todos in docusaurus.config.ts

Signed-off-by: Sivanantham Chinnaiyan <[email protected]>

* Release 0.16 docs

Signed-off-by: Sivanantham Chinnaiyan <[email protected]>

* fix: Ensure script exits on error, undefined variables, and pipe failures in release script

Signed-off-by: Sivanantham Chinnaiyan <[email protected]>

* fix: Update version comparison logic to allow equal minor versions in release script

Signed-off-by: Sivanantham Chinnaiyan <[email protected]>

* Update release process instructions

Signed-off-by: Sivanantham Chinnaiyan <[email protected]>

---------

Signed-off-by: Sivanantham Chinnaiyan <[email protected]>

Author: sivanantha321

Makefile

@@ -23,7 +23,9 @@ gen-oip-rest-api-docs:
 
 # Generate CRD API documentation for KServe master branch.
 gen-crd-api-docs:
-	./hack/crd-ref-docs/gen-crd-api-ref-docs.sh
+     # Use RELEASE_VERSION environment variable to specify the release version for which CRD docs need to be generated.
+	 # This variable is set in the release.sh script during the release process.
+	./hack/crd-ref-docs/gen-crd-api-ref-docs.sh --branch release-$(RELEASE_VERSION)
 
 # Generate Python Runtime, Control Plane SDK API documentation.
 gen-py-sdk-api-docs:

RELEASE_PROCESS.md

@@ -58,12 +58,13 @@ This document outlines the steps to create a new release for the KServe document
 ### 6. Merge and Deploy
 
 1. Once the pull request is approved, merge it into the `main` branch.
-2. Deploy the changes to the production environment.
+2. The website will automatically deploy the changes upon merging using GitHub Actions.
 
 ### 7. Post-Release Tasks
 
-1. Verify the live website to ensure the changes are reflected.
-2. Announce the new release on relevant channels (e.g., Slack, mailing list).
+1. Verify the deploy GitHub Action logs to ensure the deployment was successful.
+2. Verify the live website to ensure the changes are reflected.
+3. Announce the new release on relevant channels (e.g., Slack, mailing list).
 
 ## Notes
 

docs/getting-started/predictive-first-isvc.md

@@ -295,7 +295,5 @@ Now that you have successfully deployed your first Predictive InferenceService,
 - 📖 **[GenAI InferenceService](genai-first-isvc.md)** - Deploy your first Generative AI InferenceService
 - 📖 **[KServe Concepts](../concepts/index.md)** - Learn about the core concepts of KServe.
 - 📖 **[Supported Frameworks](../model-serving/predictive-inference/frameworks/overview.md)** - Explore Supported Frameworks.
-<!-- TODO: Uncomment once the batcher docs is migrated -->
-<!-- - 📖 **[Batch InferenceService](batch-first-isvc.md)** - Deploy your first Batch InferenceService. -->
-<!-- TODO: Uncomment once the canary docs is migrated -->
-<!-- - 📖 **[Canary Deployments](../model-serving/predictive-inference/canary-deployments/canary-deployments.md)**: Gradually roll out new model versions to test their performance before full deployment. -->
+- 📖 **[Batch InferenceService](../model-serving/predictive-inference/batcher/batcher.md)** - Deploy your first Batch InferenceService.
+- 📖 **[Canary Deployments](../model-serving/predictive-inference/rollout-strategies/canary-example.md)**: Gradually roll out new model versions to test their performance before full deployment.

docs/model-serving/predictive-inference/frameworks/huggingface/fill-mask/fill-mask.md

@@ -58,7 +58,6 @@ spec:
     - prefix: hf://
 ```
 
-<!-- TODO: Update link to refer storagecontainer docs -->
 To know more about storage containers, refer to the [Storage Containers documentation](../../../../../concepts/resources/index.md#storage-resources).
 
 ### Deploy with the V1 Protocol