From 193064e2477cea5abaea755cad54c26ff47fe734 Mon Sep 17 00:00:00 2001 From: gouravkrosx Date: Mon, 18 May 2026 15:44:10 +0000 Subject: [PATCH] =?UTF-8?q?docs(time-freezing):=20correct=20the=20Go=20ver?= =?UTF-8?q?sion=20claim=20=E2=80=94=20works=20on=20all=20supported=20Go=20?= =?UTF-8?q?releases?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The two current time-freezing pages (versions 3.0.0 and 4.0.0) both carried the same incorrect note: > Note: Time freezing is only supported till go **1.22.x** version. That hasn't been true for a while. The mechanism is build-time — `-tags=faketime` is a Go build tag that swaps `runtime.now()` to read from the freeze-time agent file instead of the OS clock — so it applies to any Go version that supports the build tag, which is every currently-supported release. Caught when an AI agent walking the Keploy MCP onboarding flow read the existing note, propagated the false "Requires Go 1.22.x" comment into a user's Dockerfile, and rejected newer Go versions. Updating the docs so the next agent (or human) reading the page gets accurate guidance. Replacement text leans positive: states the build-tag mechanism explicitly so a reader understands why the Go-version constraint doesn't apply. Scope intentionally excludes version-2.0.0 (historical / archived docs — not surfaced as current to live readers). Co-Authored-By: Claude Opus 4.7 (1M context) Signed-off-by: gouravkrosx --- versioned_docs/version-3.0.0/keploy-cloud/time-freezing.md | 4 ++-- versioned_docs/version-4.0.0/keploy-cloud/time-freezing.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/versioned_docs/version-3.0.0/keploy-cloud/time-freezing.md b/versioned_docs/version-3.0.0/keploy-cloud/time-freezing.md index 3c34acb72..006bce089 100644 --- a/versioned_docs/version-3.0.0/keploy-cloud/time-freezing.md +++ b/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 🖥️ diff --git a/versioned_docs/version-4.0.0/keploy-cloud/time-freezing.md b/versioned_docs/version-4.0.0/keploy-cloud/time-freezing.md index 97079525b..75a86ba39 100644 --- a/versioned_docs/version-4.0.0/keploy-cloud/time-freezing.md +++ b/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 🖥️