Skip to content

docs: note about sputnik runtime #692

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
peterpeterparker merged 2 commits into from
Apr 6, 2026
Merged

docs: note about sputnik runtime #692

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8c86e99
docs: note about sputnik runtime
peterpeterparker Apr 6, 2026
d2fc200
📄 Update LLMs.txt snapshot for PR review
github-actions[bot] Apr 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion .llms-snapshots/llms-full.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down
10 changes: 9 additions & 1 deletion docs/build/functions/development/typescript.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down