Releases

Current releases of each project. Source archives download straight from GitHub; the binaries & installers link opens the full GitHub release, where the platform builds and other assets live. The one-line installers below are the recommended way to get set up on Linux or Windows.

Torvik — v1.5.4

The language and compiler.

Install   Linux: curl -fsSL https://raw.githubusercontent.com/torvik-lang/torvik/main/linux/install.sh | sh Windows (PowerShell): iwr -useb https://raw.githubusercontent.com/torvik-lang/torvik/main/windows/install.ps1 | iex

Download   Binary: Linux (x86-64) · Windows (x86-64) Source: .zip · .tar.gz · all assets

What's new

v1.5.4 — "Vörðr", the watcher. A security release. Every path the compiler put on a command line went through a helper that wrapped it in double quotes — which do not stop command substitution, so $(...) and backticks expanded. Confirmed through the -o output path and through HOME. The helper now refuses shell syntax rather than quoting it, covering all seventeen call sites at once. This is the seventh and last of a family of injection issues; the advisory explains what changed beyond the fix, and why anyone writing wrappers around torvc should check their own. Update if you run torvc from scripts, CI, or anywhere HOME is set from configuration.

v1.5.3 — "Stillbót", a quiet mending. A security fix and five correctness bugs, no feature changes. torvc run refused to pass arguments containing shell syntax after an injection was found; hex escapes outside printable ASCII no longer vanish ("\x1b[2J" kept its escape character); list<f64> elements can be assigned; readint and readfloat no longer read freed memory when rejecting bad input; fmt prints 128-bit values rather than their address; and three builtins stopped reporting themselves as undefined when called with the wrong argument count. A new narrowing warning points at width conversions that 1.x does not enforce. See the changelog and advisory.

"The Forge" — systems and OS development. Torvik can now build a freestanding image that boots on bare hardware, with no operating system, no C library, and no runtime beneath it. Everything new here is opt-in and unsafe-gated; the safe surface is unchanged.

• Raw pointers (varda<T>), bounds-checked fixed arrays ([T; N]), and shape value

structs — a packed shape maps byte-for-byte onto a C struct or hardware descriptor

• size_of / align_of, volatile MMIO (load_vol / store_vol), inline assembly

(galdr), and named x86_64 port intrinsics

• torvc --bare freestanding builds, with an allocator hook so heap types work bare —

plus a complete reference kernel and tutorial

• Float widths f16, f32, f128 alongside f64, with true storage layout
• Hex, binary and underscored integer literals — 0xB8000, 0b1010_0110, 1_000_000
• Run mode: torvc file.tv executes a file directly, no binary left behind
• The standard library moved to its own repository
• && and || now short-circuit — a correctness fix; they previously evaluated both

sides, so i < len(xs) && xs[i] == 1 could read out of bounds

• Many fixes, including several cases where a user mistake was reported as an internal

compiler error

All Torvik releases →

rune — v1.5.0

The project and toolchain manager. Normally installed with Torvik; see the rune page for the full command set.

Install (rune only)   Linux: curl -fsSL https://raw.githubusercontent.com/torvik-lang/rune/main/linux/install.sh | sh Windows (PowerShell): iwr -useb https://raw.githubusercontent.com/torvik-lang/rune/main/windows/install.ps1 | iex

Download   Binary: Linux (x86-64) · Windows (x86-64) Source: .zip · .tar.gz · all assets

What's new

• rune run <file.tv> [args...] runs a single file directly, forwarding arguments
• A [build] manifest section — declare a freestanding target once and rune build /

rune run build and launch a kernel

• Major-version gating: updates stay inside your current major and report a new one

instead of installing it (rune update v2 --yes opts in)

• Standard-library gating, with rune update --std-major --yes writing the pin into your

manifest for you

• rune now has its own test suite, so it can be checked without building the compiler

v1.4.0 is rune's first release in its own repository. Earlier rune versions (v1.3.0 and before) shipped as part of Torvik — find those binaries under the matching Torvik release assets. If you're on an older Torvik, you already have the rune that came with it; rune update moves you to the latest of both.

All rune releases →

Vefna — v1.1.0

The static site generator woven in Torvik.

Install   Linux: curl -fsSL https://raw.githubusercontent.com/torvik-lang/vefna/main/linux/install.sh | sh Windows (PowerShell): iwr -useb https://raw.githubusercontent.com/torvik-lang/vefna/main/windows/install.ps1 | iex

Download   Binary: Linux (x86-64) · Windows (x86-64) Source: .zip · .tar.gz · all assets

What's new

• vefna serve [port] — a built-in preview server with rebuild-on-change
• vefna watch / vefna build --watch — rebuild continuously as sources change
• --drafts — draft: true pages are skipped unless you ask for them
• Built with Torvik v1.4.0

All Vefna releases →

Looking for older versions or full changelogs? Every project's releases page lists each version with its notes and downloads.

Support policy

Every major version is supported for five years, in three stages:

| Stage | Years | What it gets | | --- | --- | --- | | Active | 0 – 3 | New features, bug fixes, security fixes. Minor releases happen here. | | Maintenance | 3 – 4 | Bug fixes and security fixes. No new features. | | Security | 4 – 5 | Security fixes only. |

Where things stand

| Line | Released | Stage | Active until | Maintenance until | End of life | | --- | --- | --- | --- | --- | --- | | Torvik 1.x | 4 Jul 2026 | Active | 4 Jul 2029 | 4 Jul 2030 | 4 Jul 2031 | | rune 1.x | 4 Jul 2026 | Active | 4 Jul 2029 | 4 Jul 2030 | 4 Jul 2031 | | Vefna 1.x | 4 Jul 2026 | Active | 4 Jul 2029 | 4 Jul 2030 | 4 Jul 2031 |

The standard library versions independently but tracks the toolchain line it ships with: std 1.x is supported for as long as Torvik 1.x is.

Nothing stops working at end of life — a compiler that built your program last year will build it next year. What ends is the flow of updates.

You are never rushed onto a new major. rune update deliberately keeps you inside your current major and only tells you a new one exists, so a 1.x project keeps receiving fixes for five years whether or not 2.0 has shipped. Upgrading stays a decision you make, not one made for you.

Full policy: SUPPORT.md