Merge branch 'main' into add-ruby-postgresql-quickstart

Author: Nsanjayboruds

versioned_docs/version-3.0.0/keploy-cloud/time-freezing.md

@@ -50,11 +50,11 @@ For Docker-based applications, you'll need to make a few adjustments to your Doc
 uname -a
 ```
 
-2. Download the the appropriate time freeze agent for your architecture & set the `LD_PRELOAD` Environment Variable in your Dockerfile
+2. Download the appropriate time freeze agent for your architecture & set the `LD_PRELOAD` Environment Variable in your Dockerfile
 
 ### For Golang(Go) Applications -
 
-> Note: Time freezing is only supported till go **1.22.x** version.
+> Note: Time freezing works on every Go version that supports the `faketime` build tag, i.e. all currently supported Go releases. The mechanism is build-time (the `-tags=faketime` flag swaps Go's `time` package to read from a runtime agent file instead of the OS clock), so it's not tied to any specific Go version.
 
 #### amd64/x86_64 🖥️
 

versioned_docs/version-4.0.0/keploy-cloud/time-freezing.md

@@ -51,11 +51,11 @@ For Docker-based applications, you'll need to make a few adjustments to your Doc
 uname -a
 ```
 
-2. Download the the appropriate time freeze agent for your architecture & set the `LD_PRELOAD` Environment Variable in your Dockerfile
+2. Download the appropriate time freeze agent for your architecture & set the `LD_PRELOAD` Environment Variable in your Dockerfile
 
 ### For Golang(Go) Applications -
 
-> Note: Time freezing is only supported till go **1.22.x** version.
+> Note: Time freezing works on every Go version that supports the `faketime` build tag, i.e. all currently supported Go releases. The mechanism is build-time (the `-tags=faketime` flag swaps Go's `time` package to read from a runtime agent file instead of the OS clock), so it's not tied to any specific Go version.
 
 #### amd64/x86_64 🖥️
 

versioned_docs/version-4.0.0/quickstart/k8s-proxy-developer-workflow.md

@@ -193,10 +193,12 @@ jobs:
           KEPLOY_API_KEY: ${{ secrets.KEPLOY_API_KEY }}
         run: |
           keploy cloud branch-merge \
-            --app <app-id> \
+            --app <namespace>.<deployment> \
             --branch ${{ github.head_ref }}
 ```
 
+`--app` accepts either a `namespace.deployment` identifier (k8s-proxy apps, e.g. `prod.orders`) or a raw app UUID (non-proxy apps). The same form you use for `keploy upload test-set` and `keploy cloud replay` works here.
+
 `keploy cloud branch-merge` is idempotent—running it twice on an already-merged branch is a no-op. If the PR was closed without merging, the `if:` guard above keeps the job from firing.
 
 ---