Skip to content

Commit fa48a60

Browse files
docs: note about sputnik runtime (#692)
* docs: note about sputnik runtime Signed-off-by: David Dal Busco <david.dalbusco@outlook.com> * 📄 Update LLMs.txt snapshot for PR review --------- Signed-off-by: David Dal Busco <david.dalbusco@outlook.com> Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
1 parent 947913a commit fa48a60

File tree

2 files changed

+18
-2
lines changed

2 files changed

+18
-2
lines changed

.llms-snapshots/llms-full.txt

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3047,9 +3047,17 @@ For example, if you're on **v0.0.23** and the latest release is **v0.0.26**, fir
30473047

30483048
---
30493049

3050+
## Runtime
3051+
3052+
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.
3053+
3054+
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.
3055+
3056+
---
3057+
30503058
## Versioning
30513059

3052-
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.
3060+
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.
30533061

30543062
By default, the version is inherited from the root-level `version` field:
30553063

docs/build/functions/development/typescript.mdx

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,17 @@ import Caution from "./components/upgrade-caution.mdx";
3030

3131
---
3232

33+
## Runtime
34+
35+
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.
36+
37+
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.
38+
39+
---
40+
3341
## Versioning
3442

35-
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.
43+
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.
3644

3745
By default, the version is inherited from the root-level `version` field:
3846

0 commit comments

Comments
 (0)