Skip to content

RunR 0.6.2

Choose a tag to compare

@brkfun brkfun released this 26 Oct 15:51
· 50 commits to main since this release
v0.6.2

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.6.2 is a maintenance release of 0.6.1. Its images are the first that this repository's own GitHub Actions workflow, release-images.yml, built and pushed: linux/amd64 and linux/arm64 on runners of their own, every image labelled with RunR's own OCI metadata and linked to this repository. The API image carries the documentation for the MCP server's runr://docs resources again, and the Terraform provider is on the Terraform Registry as brf-tech/runr. It adds no Helm values and no new database migrations. CHANGELOG.md has the complete history. Downloads 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.6.2; 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.6.2 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.6.2/) 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.6.2; 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.6.1

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.6.1 nothing has to be decided or set: 0.6.2 adds no Helm values and no new database migrations, and the images keep their names (0.6.1 → 0.6.2 in docs/upgrade.md).

helm repo update brf-tech
helm upgrade runr brf-tech/runr --version 0.6.2 -n runr --reuse-values
  • The region agent and the event gateway move to 0.6.2. As in 0.6.0 and 0.6.1, they run at the installed version: after helm upgrade returned, the Job runr-region-reconcile-<revision> moves the regions' agents (also the internal network's authz), queue consumers and topic publishers from agent:0.6.1 / queue-consumer:0.6.1 to ghcr.io/brf-tech/runr/agent:0.6.2 and queue-consumer:0.6.2; each rolls once. A region that pulls through a mirror of your own needs these two images there before the upgrade (Order of operations).
  • Back to 0.6.1: a plain helm rollback (or helm upgrade with the 0.6.1 chart where only one package version is kept) on the same database; the region Job of the 0.6.1 chart moves the region images back to 0.6.1.
  • Terraform provider 0.6.2 has the resources and data sources of 0.6.1; its address on the Terraform Registry is registry.terraform.io/brf-tech/runr. Configurations on runr.sh/brf-tech/runr keep working and pick it up with terraform init -upgrade. Moving one to source = "brf-tech/runr" is optional: terraform state replace-provider runr.sh/brf-tech/runr registry.terraform.io/brf-tech/runr once, then terraform init (docs/terraform.md#install).

From 0.6.0, upgrade straight to 0.6.2 and 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 and 0.6.1 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.6.2 (2026-10-26)

Upgrade notes

No new database migrations and no new Helm values; values of 0.6.1, --reuse-values included,
keep working (0.6.1 → 0.6.2 in upgrade.md). The region agent and the
queue consumer follow the release (0.6.2); gateway-auth, image-upload, supply-chain and the Spin
shim keep their versions.

Changed

  • The Terraform provider is on the Terraform Registry as brf-tech/runr. With
    source = "brf-tech/runr", terraform init downloads the archive from the provider's GitHub
    release and checks it against the release's SHA256SUMS, signed with the RunR release key (key
    ID 2588846B241BC095). runr.sh keeps serving the latest release, the same signed archives,
    under runr.sh/brf-tech/runr, for OpenTofu and for configurations that use that address.
    Moving a configuration over is optional: change source, run
    terraform state replace-provider runr.sh/brf-tech/runr registry.terraform.io/brf-tech/runr
    once, then terraform init (docs/terraform.md). The provider's
    debug address and make install (PLUGIN_HOST, default registry.terraform.io) follow.
  • The release images are built and pushed by the repository's own GitHub Actions workflow.
    .github/workflows/release-images.yml runs on the release tag v<version> with the
    repository's GITHUB_TOKEN: api, ui and ui:<version>-mt, and the region images of
    runtime/ci.sh release-images the registry does not have yet. linux/amd64 and linux/arm64 build
    on runners of their own (no emulation), are pushed by digest and composed into multi-arch tags;
    latest moves only to the highest release tag; the last job pulls every tag without
    credentials. Every image labels RunR's own OCI metadata in place of its base image's
    (org.opencontainers.image.source=https://github.com/BRF-Tech/runr, title, description,
    version, revision, created, licenses) and every index carries it as annotations, so each
    package on ghcr.io is linked to the repository. The run's artifact runr-<version>-tars holds
    the amd64 image tars of api, ui and ui-mt (the pushed images, byte for byte), the chart and
    SHA256SUMS. The GitLab pipeline builds and pushes no image any more; its test jobs stay
    (development.md). ci/check-dockerfiles.sh fails on an image
    that does not label the source.

Fixed

  • The MCP server's documentation resources are in the API image again. The released API image
    had no resources/docs (the release builds did not copy docs/ into it, 0.6.1 included), so
    runr://docs/{page} found no page unless MCP_DOCS_PATH or a docs/ next to the API was set
    up. The release workflow copies docs/*.md into the image, as compose/build.sh and
    ci.sh build-deploy do (mcp.md).