Skip to content

RunR 0.5.10

Choose a tag to compare

@brkfun brkfun released this 21 Oct 09:24
· 59 commits to main since this release
v0.5.10

RunR is an open-source, self-hosted serverless platform on Kubernetes and Knative: functions, containers, sandboxes, WebAssembly and durable workflows, with an API, a web console, the runr CLI, SDKs, a Terraform provider and a GitHub Action. You install it on infrastructure you operate, connected or air-gapped. It is developed by BRF Teknoloji and released under the MIT License.

0.5.10 moves the runtime images into their own repository, BRF-Tech/runr-runtimes, which builds, smoke-tests and publishes them under the same names and tags, and makes a region migration rollback remove the projects' workloads from the cluster it leaves. CHANGELOG.md has the complete history. Downloads, the Terraform provider registry and the documentation are on runr.sh.

Install

  • Kubernetes (Helm): the chart comes from BRF's public Helm repository, without credentials:
    helm repo add brf-tech https://helm.brf.sh
    helm upgrade --install runr brf-tech/runr --namespace runr --create-namespace --set domain=runr.example.com
    See the README and docs/install.md; helm show values brf-tech/runr lists every value. A pinned install adds --version 0.5.10; the API and UI images follow the chart version.
  • Single host (Docker Compose, also air-gapped): compose/README.md, from a checkout of the release tag (git clone -b v0.5.10 https://github.com/BRF-Tech/runr.git).
  • CLI: curl -fsSL https://runr.sh/install.sh | sh on Linux and macOS. The archives of every platform are at runr.sh/dl (https://runr.sh/dl/cli/v0.5.10/) and attached below; check them against checksums.txt (docs/cli.md#install).
  • Terraform / OpenTofu: source = "runr.sh/brf-tech/runr". runr.sh serves the provider registry protocol; terraform init checks the archive against SHA256SUMS, signed with the RunR release key (key ID 2588846B241BC095) (docs/terraform.md#install).
  • GitHub Action: uses: brf-tech/runr/actions/deploy@v0.5.10; it downloads the CLI from runr.sh (docs/github-action.md).
  • Images: every image is published under ghcr.io/brf-tech/runr and pulls anonymously.

The documentation is at runr.sh/docs and in the documentation index here.

Upgrading

Upgrade in place with helm upgrade of the running release; never uninstall and install again, and back up the database first (Procedure in docs/upgrade.md). From 0.5.9 nothing special is needed: 0.5.10 adds no values and no database migrations.

helm repo update brf-tech
helm upgrade runr brf-tech/runr --version 0.5.10 -n runr --reuse-values

The runtime images (the language and ML runtimes, the WebAssembly build images, the universal wrapper and hf-serve) and the reqs mirror (ghcr.io/brf-tech/runr/reqs/) now come from BRF-Tech/runr-runtimes. Their names and tags under ghcr.io/brf-tech/runr are unchanged, so installs and the API's runtime discovery see no change (Built-in catalog in docs/runtimes.md).

From 0.5.8 or earlier: the image tags stored in the release stay, so add --set api.image.tag= --set ui.image.tag= to that upgrade once and both tags follow the chart from then on (step 3 of the Procedure). Read the notes of the releases in between in CHANGELOG.md as well, 0.5.7 → 0.5.8 in particular.

Changes in 0.5.10 (2026-10-21)

Changed

  • The runtime images have their own repository,
    BRF-Tech/runr-runtimes.
    It holds the language and
    ML runtimes (exec-python, -nodejs, -go, -php, -pytorch, -tensorflow), the WebAssembly
    build images (exec-wasm-*), the universal wrapper, hf-serve, the manifests of the built-in
    catalog and the reqs mirror (ghcr.io/brf-tech/runr/reqs/). Its GitHub Actions build,
    smoke-test and publish them under the same names and tags, so installs and the API's runtime
    discovery see no change.
    • runtime/ keeps RunR's own images (agent, queue consumer, image-upload, supply-chain tools,
      the Spin shim, nginx-test) and the end-to-end harness.
    • The API ships the catalog as before (api/resources/runtimes/builtin.json). After a manifest
      changes in runr-runtimes, RUNR_RUNTIME_CATALOG=<checkout>/runtimes php artisan runtimes:bundle regenerates it.
    • runtime/ci.sh build, wrapper, wasm, ml-runtimes, mirror-reqs, mirror-bases and eol
      moved there, and the GitLab jobs build:runtime and build:ml-runtimes are gone.
  • The Kind e2e suites pull the published runtime images instead of building them.
    • test-runtimes pulls the wrapper, test-wasm the Rust and JavaScript build images,
      test-images wasm-exec and test-ai hf-serve, at the tags pinned in
      runtime/lib/runtime-images.sh.
    • runtime/test/runtime_images_test.sh checks that these pins are the product's defaults.
    • RUNTIME_IMAGES_LOCAL=1 uses a local build from runr-runtimes instead.
  • ci/check-reqs-mirror.sh resolves every referenced reqs image anonymously on ghcr.io
    instead of looking it up in a mirror list. Resolved references are cached for a day. A missing
    image says where to add it in runr-runtimes, and a network error is reported apart from missing
    images.

Fixed

  • A region migration rollback left the projects running on the new cluster. The rollback
    deployed the projects on the old cluster again, but what the move had deployed for them on the
    new cluster kept running there: their functions answered on that cluster's own address, and
    nothing metered them. After a rollback RunR now removes them from the new cluster in the
    background — the Knative Services of the projects and of their previews, their CronJobs and
    queue consumers, and the ConfigMaps, Secrets and build Jobs these read or built — found by the
    labels RunR sets, for the projects of every organization on a platform region and for a project
    created while the region ran there. The cluster's installs and the data services with their
    volumes, credentials and data stay: they may hold what was written during the move. Nothing is
    removed when the new cluster is the restored one under another address (the same kube-system
    namespace). The removal does not hold the rollback up and is tried three times; the operator who
    rolled back gets a notification with what was removed, or with the reason and what to remove by
    hand (What the rollback removes from the new
    cluster
    ).