Skip to content

RunR 0.7.3

Choose a tag to compare

@brkfun brkfun released this 14 Nov 20:01
· 7 commits to main since this release
v0.7.3

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.7.3 changes nothing an installation runs: it carries a fix of RunR's dependency test bot and a link to the live demo.

Added: runr.sh and the README point to the live demo, demo.runr.sh: a read-only RunR that resets every night (sign in with demo@runr.sh / runr-demo).

When one bump of a run went red, the bot skipped the combined tests of the others, so 0.7.2 released only the first green bump of each path; it now tests its green bumps together after a red one (docs/development.md). The API's tenancy ticket list no longer calls array_values() on a list, which did nothing and which Larastan 3.15 reports as an error; the response is the same. The release workflow's docker/login-action moves to v4.8.0.

Upgrading from 0.7.2 changes the version only: no migration, no new value, the images of 0.7.2 built again at 0.7.3.

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.7.3; the API and UI images, the region agent and the event gateway 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.7.3 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.7.3/) and attached below; check them against checksums.txt (docs/cli.md#install).
  • Terraform / OpenTofu: source = "brf-tech/runr", version = "~> 0.6", from the Terraform Registry; terraform init checks the archive against SHA256SUMS, signed with the RunR release key (key ID 2588846B241BC095). runr.sh serves the same archives under runr.sh/brf-tech/runr, for OpenTofu and for configurations that use that address (docs/terraform.md#install).
  • GitHub Action: uses: brf-tech/runr/actions/deploy@v0.7.3; it downloads the CLI from runr.sh (docs/github-action.md).
  • Images: every image is published under ghcr.io/brf-tech/runr by release-images.yml, for linux/amd64 and linux/arm64, and pulls anonymously.

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

Upgrading from 0.7.2

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). The images keep their names and nothing has to be set (0.7.2 → 0.7.3).

helm repo update brf-tech
helm upgrade runr brf-tech/runr --version 0.7.3 -n runr --reuse-values
  • Nothing an installation runs changes. The console, the region agent and the event gateway are those of 0.7.2 at the version 0.7.3, and the API is 0.7.2's but for that one line. As in every release, after helm upgrade returned, the Job runr-region-reconcile-<revision> moves the regions' agents, queue consumers and topic publishers to ghcr.io/brf-tech/runr/agent:0.7.3 and queue-consumer:0.7.3; each rolls once. A region that pulls through a mirror of its own needs these two images there before the upgrade (Order of operations).
  • Back to 0.7.2: a helm rollback; nothing runs on the database (Back to 0.7.2).
  • CLI and Terraform provider 0.7.3: the code of 0.7.1's (0.7.2, a dependency release, shipped neither); the provider's resources and data sources are the ones of 0.6.10.

From 0.7.1, upgrade straight to 0.7.3: 0.7.2 only moved Go modules of the region agent and needs no step either (0.7.1 → 0.7.2). From 0.7.0, upgrade straight to 0.7.3 and read 0.7.0 → 0.7.1 first: --reuse-values keeps the scheduler at the 64Mi / 256Mi of the old chart, so add --set scheduler.resources.requests.memory=160Mi --set scheduler.resources.limits.memory=512Mi to that upgrade (or upgrade with --reset-then-reuse-values); the same holds for every release before 0.7.1 below. From 0.6.13, upgrade straight to 0.7.3 and read 0.6.13 → 0.7.0 first: 0.7.0 adds two migrations (knative_regions.kubernetes_version, and the existing wasm-rust and wasm-js projects without a runtime version pinned to 4.1), runs Helm 4 for the region releases (Helm 4) and the kubectl of each region's Kubernetes minor (kubectl per region), and moves gateway-auth to 1.1.0 and the Spin shim to v0.27.2-runr.1; a rollback to 0.6.13 needs the projects moved to WebAssembly 4.2 set back to 4.1 first (Back to 0.6.13). From 0.6.10 to 0.6.12, upgrade straight to 0.7.3 and read 0.6.13 → 0.7.0 as well: 0.6.11 and 0.6.13 only moved Go modules of a region image (the queue consumer's and image-upload's, the security update of github.com/klauspost/compress, GO-2026-6865, among them) and 0.6.12 fixed RunR's release tooling; none of them needs a step (0.6.12 → 0.6.13, 0.6.11 → 0.6.12, 0.6.10 → 0.6.11). From 0.6.0 to 0.6.9, upgrade straight to 0.7.3 and read the security release 0.6.9 → 0.6.10 first: after the upgrade, check the routes of every project in access mode allowlist (After the upgrade). From 0.6.8, also read 0.6.8 → 0.6.9: 0.6.9 adds a column (projects.capacity_released_at, and in every tenant schema), a stopped project gives its capacity back in a pay-as-you-go region and is admitted again on resume, and a region with many stopped projects can raise the capacity alarm right after the upgrade. From 0.6.7, also read 0.6.7 → 0.6.8: 0.6.8 adds runtime sources and RunR's signed runtime catalog, which the API reads from ghcr.io (runtimeCatalog.offline: true keeps the bundled one), gives single-tenant Owners platform.manage, moves the region Traefik to chart 42.3.1, and a marketplace that merges the package's default values into an upgrade can bring ingress.tls.mode: letsencrypt to a release that never set it (The console certificate warning). From 0.6.6, also read 0.6.6 → 0.6.7: 0.6.7 changes how sandbox commands travel on Kata and gVisor (a command on gVisor takes about 100 ms more), input that arrives short fails, and a custom sandbox image needs cat and mkfifo. From 0.6.5, also read 0.6.5 → 0.6.6: 0.6.6 re-runs kata-deploy with Kata Containers 4.3.1, which stops the running Kata pods of every region with Kata, the region Traefik moves to chart 42.3.0 and deletes request headers with _ or . in their names, and Reverb refuses client events. From 0.6.4, also read 0.6.4 → 0.6.5: 0.6.5 adds the notification_user_states migration, the Helm value notifications.retentionDays, and its daily task deletes notifications older than 90 days. From 0.6.3, also read 0.6.3 → 0.6.4: 0.6.4 adds the captcha_settings migration and the Helm values captcha.*, and its first upgrade rolls the pods once. From 0.6.2, also read 0.6.2 → 0.6.3; from 0.6.1, also 0.6.1 → 0.6.2. From 0.6.0, also read 0.6.0 → 0.6.1 first: before a rollback to 0.6.0, let the running deploys finish (Rolling back to 0.6.0). From 0.5.10, read 0.5.10 → 0.6.0 in docs/upgrade.md first — in particular what to decide before the upgrade — and the notes of 0.6.0 to 0.6.9 in CHANGELOG.md; everything said there applies. From 0.5.9 or earlier, read the notes of the releases in between as well; from 0.5.8 or earlier, add --set api.image.tag= --set ui.image.tag= to that upgrade once (step 3 of the Procedure).

Changes in 0.7.3 (2026-11-14)

Upgrade notes

  • Nothing an installation runs changes: upgrading from 0.7.2 changes the version only. No
    migration, no new value; the images of 0.7.2 are built again at 0.7.3 (the API's with one line
    less that did nothing: the tenancy ticket list no longer calls array_values() on a list, and
    its response is the same), and the region Job moves the agent and the event gateway to 0.7.3 as
    in every release (0.7.2 → 0.7.3 in upgrade.md).
  • Back to 0.7.2 is a helm rollback; nothing runs on the database.

Added

  • runr.sh and the README point to the live demo. demo.runr.sh, a read-only RunR that resets
    every night, gets a Live demo button in runr.sh's hero (and its mobile menu, English and
    Turkish) with the sign-in under it (demo@runr.sh / runr-demo), and a badge and a line at the
    top of README.md and README.tr.md. Until now nothing linked to it.

Changed

  • GitHub Actions pins moved (minor and patch updates, nothing a release image ships):
    docker/login-action v4.6.0 → v4.8.0.

Fixed

  • The dependency test bot tests its green bumps together even when one of the run's bumps went
    red.
    The combined-tree jobs had no status function in their if, so GitHub skipped them after
    any red bump of the first phase. The bot then read the missing results as a failure: 0.7.2 took
    only the first green bump of each path, and two bumps that passed (#78 zot 0.1.134, #30 go-cli)
    were labelled "needs attention". A combined job that leaves no result now blames no bump: the
    first goes, the others wait for the next run with no label.