diff --git a/.llms-snapshots/llms-full.txt b/.llms-snapshots/llms-full.txt
index 9ba53aa7..5acc9bcd 100644
--- a/.llms-snapshots/llms-full.txt
+++ b/.llms-snapshots/llms-full.txt
@@ -3047,9 +3047,17 @@ For example, if you're on **v0.0.23** and the latest release is **v0.0.26**, fir
 
 ---
 
+## Runtime
+
+When building TypeScript serverless functions, the runtime version is always **the one bundled in the tool** you are using — the emulator or the GitHub Action. It is not a dependency you declare or control in your project.
+
+This means the runtime is tied to the image version. Keeping the emulator and GitHub Action up to date is the way to get the latest runtime features and fixes.
+
+---
+
 ## Versioning
 
-When writing serverless functions in TypeScript, Juno uses the version defined in your project’s `package.json`. This version is embedded into the compiled Wasm module and shown in the Juno Console, making it easier to keep track of deployments.
+Juno uses the version defined in your project’s `package.json`. This version is embedded into the compiled Wasm module and shown in the Juno Console, making it easier to keep track of deployments.
 
 By default, the version is inherited from the root-level `version` field:
 
diff --git a/docs/build/functions/development/typescript.mdx b/docs/build/functions/development/typescript.mdx
index b4d893ce..8ee7cb6d 100644
--- a/docs/build/functions/development/typescript.mdx
+++ b/docs/build/functions/development/typescript.mdx
@@ -30,9 +30,17 @@ import Caution from "./components/upgrade-caution.mdx";
 
 ---
 
+## Runtime
+
+When building TypeScript serverless functions, the runtime version is always **the one bundled in the tool** you are using — the emulator or the GitHub Action. It is not a dependency you declare or control in your project.
+
+This means the runtime is tied to the image version. Keeping the emulator and GitHub Action up to date is the way to get the latest runtime features and fixes.
+
+---
+
 ## Versioning
 
-When writing serverless functions in TypeScript, Juno uses the version defined in your project’s `package.json`. This version is embedded into the compiled Wasm module and shown in the Juno Console, making it easier to keep track of deployments.
+Juno uses the version defined in your project’s `package.json`. This version is embedded into the compiled Wasm module and shown in the Juno Console, making it easier to keep track of deployments.
 
 By default, the version is inherited from the root-level `version` field: