From 5c40cc181f8ca681e18e74c2a01faeb0f5a805e2 Mon Sep 17 00:00:00 2001
From: xuelianhan007 <148412906+xuelianhan007@users.noreply.github.com>
Date: Mon, 23 Dec 2024 10:50:40 +0800
Subject: [PATCH 1/2] fix(sdk): added checking for empty string (#314)

* added checking rules for empty string
---
 .../kraken/operator/gateway/runner/DataTypeChecker.java  | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/kraken-java-sdk/kraken-java-sdk-gateway/src/main/java/com/consoleconnect/kraken/operator/gateway/runner/DataTypeChecker.java b/kraken-java-sdk/kraken-java-sdk-gateway/src/main/java/com/consoleconnect/kraken/operator/gateway/runner/DataTypeChecker.java
index bd6bbeed..0025a63e 100644
--- a/kraken-java-sdk/kraken-java-sdk-gateway/src/main/java/com/consoleconnect/kraken/operator/gateway/runner/DataTypeChecker.java
+++ b/kraken-java-sdk/kraken-java-sdk-gateway/src/main/java/com/consoleconnect/kraken/operator/gateway/runner/DataTypeChecker.java
@@ -70,6 +70,15 @@ default boolean checkExpectString(PathCheck pathCheck, Object variable) {
               variable,
               (dataType == null ? null : dataType.getSimpleName()),
               "String"));
+    } else if (StringUtils.isBlank((String) variable)) {
+      throwException(
+          pathCheck,
+          String.format(
+              EXPECT_INT_MSG,
+              extractCheckingPath(pathCheck.path()),
+              variable,
+              "empty string",
+              "Non Empty String"));
     }
     return true;
   }

From c77d99e4702430cbb8bf5a6927a411e43e0dafa8 Mon Sep 17 00:00:00 2001
From: miya chen <51311083+miyaflowercat@users.noreply.github.com>
Date: Mon, 23 Dec 2024 13:34:17 +0800
Subject: [PATCH 2/2] Update release_schedule.md

---
 release_schedule.md | 22 +++++++++++++---------
 1 file changed, 13 insertions(+), 9 deletions(-)

diff --git a/release_schedule.md b/release_schedule.md
index 1433f9ce..973f961d 100644
--- a/release_schedule.md
+++ b/release_schedule.md
@@ -1,10 +1,10 @@
-# Main Branch
+# Main Branch Versions
 
-In main branch it only maintains **snapshot versions** and the first **rc version** of major releases.
+In main branch it only maintains **snapshot versions** of major releases.
 
-A new major version’s first snapshot version will start right after the previous major version’s release branch is made and the main branch typically will bumped into a snapshot version like 2.0.0-snapshot.0, 3.0.0-snapshot.0 .
+A new major version’s first snapshot version will start right after the previous major version’s release branch is made and the main branch typically will bumped into a snapshot version like 2.0.0-snapshot.0, 3.0.0-snapshot.0 etc.
 
-## 2.0.0
+## 2.0.0 release schedule in Main branch
 
 | Version          | Release Content       | Target Release Date  | Actual Release Date |
 | -----------------|:---------------------| --------------------:|--------------------:|
@@ -19,14 +19,18 @@ A new major version’s first snapshot version will start right after the previo
 | 2.0.0-snapshot.8 | - to be added               |      Feb-24-2024     |                     |
 | 2.0.0-snapshot.9 | - to be added               |      Mar-03-2024     |                     |
 | 2.0.0-snapshot.10 | - to be added               |      Mar-10-2024     |                     |
-| 2.0.0-rc.0 | - to be added               |      Mar-17-2024     |                     |
+| 2.0.0-snapshot.11 | - to be added               |      Mar-17-2024     |                     |
 
-# v1 Release Branch
+# Release Branch Versions
 
-Each major release(x.0.0) will have a dedicated release branch, the timing to create the release branch is when the first rc version(rc.0) of x.0.0 is created in main branch.
-- When a release branch is created, it inherits the latest version number from the main.
+Each major release(x.0.0) will have a dedicated release branch, the timing to create the release branch for x.0.0 is when the last snapshot release of it is created in main branch.
+- The release branch of x.0.0 will be named with v{{x}}, e.g. v1, v2, v3 .....
+- After a release branch is created, it will be bumped into the rc.0 version of x.0.0, e.g. 1.0.0-rc.0.
 - Since version of rc.0, only critical bug fixes and any security issues are added to the release branch going forward until release x.0.0 is made.
-- After release of x.0.0 is made in release branch, any bug fixes or minor features added to the release branch increment the minor version.
+- After release of x.0.0 is made in release branch, any further bug fixes or minor features added to the release branch will increment the minor version which will be carefully planned depending customer issues.
+
+
+## Release Schedule in v1 Release Branch
 
 v1 release branch is maintaining all the releases related with 1.0.0.