Repository navigation
RunR 0.6.5
What's new in 0.6.5
- Dependency updates for published advisories: the console's code editor sanitizes with DOMPurify 3.4.17 instead of the older copy Monaco ships (a critical advisory among them); the console takes vue-i18n 11 and follow-redirects 1.16.2, the API symfony/mime 7.4.22.
- Revoking the other sessions no longer ends the user's API tokens, and every user can list and revoke their own API tokens and connected MCP clients.
- The API reference at
/api/docsopens again: the API image builds its OpenAPI document once, and every operation has a group, a one-line summary and an operationId of its own.
One new database migration and one new Helm value, notifications.retentionDays (default 90): values of 0.6.4 keep working, and in-app notifications older than the retention are deleted after the upgrade, so set it first to keep them longer. Upgrade with:
helm repo update
helm upgrade runr brf-tech/runr --version 0.6.5 --namespace runr --reuse-valuesUpgrade notes: docs/upgrade.md. Full changes below and in CHANGELOG.md. CLI archives for Linux, macOS and Windows (amd64, arm64) are attached; checksums.txt lists their SHA-256.
Demo: https://demo.runr.sh (credentials are on the sign-in page).
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.5 is a maintenance release of 0.6.4. It takes the dependency updates for published advisories: the console's code editor sanitizes with DOMPurify 3.4.17 instead of the older copy Monaco ships (a critical advisory among them), and the console takes vue-i18n 11 and follow-redirects 1.16.2, the API symfony/mime 7.4.22. Revoking the other sessions under Active Sessions no longer ends the user's API tokens, and every user can list and revoke their own API tokens and connected MCP clients; creating one still needs the permission. The API reference at /api/docs opens again: the API image builds its OpenAPI document once, so /api/docs and /api/docs.json answer in milliseconds instead of running into the 30-second limit of a request, and the image carries the Scalar viewer the page loads; each of its 677 operations is in one of 54 groups, with a one-line summary and an operationId of its own. The UI image sends its files pre-compressed instead of compressing every response. The transfer agent (image-upload 1.1.1) no longer loses a failed pull's reason or a pull's result, the sign-in page asks for SSO providers only when the AuthProvider module is on, the CAPTCHA widget is light on the light sign-in cards, and the console no longer shows message keys while it starts. Each member now marks the shared notifications read or deletes them for themselves, where one member's Mark all as read or Delete all changed them for everyone. Notifications are deleted after a retention, 90 days by default, and a deleted account's notifications go with it. 0.6.5 adds one database migration, notification_user_states, and one Helm value, notifications.retentionDays. 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:
See the README and docs/install.md;
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
helm show values brf-tech/runrlists every value. A pinned install adds--version 0.6.5; 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.5 https://github.com/BRF-Tech/runr.git). - CLI:
curl -fsSL https://runr.sh/install.sh | shon Linux and macOS. The archives of every platform are at runr.sh/dl (https://runr.sh/dl/cli/v0.6.5/) and attached below; check them againstchecksums.txt(docs/cli.md#install). - Terraform / OpenTofu:
source = "brf-tech/runr",version = "~> 0.6", from the Terraform Registry;terraform initchecks the archive againstSHA256SUMS, signed with the RunR release key (key ID2588846B241BC095). runr.sh serves the same archives underrunr.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.5; it downloads the CLI from runr.sh (docs/github-action.md). - Images: every image is published under
ghcr.io/brf-tech/runrby 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.4
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.4 nothing has to be set: 0.6.5 adds one database migration, notification_user_states, which the pre-upgrade migration Job runs, and one Helm value, notifications.retentionDays (default 90; reused values of 0.6.4 render 90), and the images keep their names (0.6.4 → 0.6.5 in docs/upgrade.md).
helm repo update brf-tech
helm upgrade runr brf-tech/runr --version 0.6.5 -n runr --reuse-values- The region agent and the event gateway move to 0.6.5. As in 0.6.0 to 0.6.4, they run at the installed version: after
helm upgradereturned, the Jobrunr-region-reconcile-<revision>moves the regions' agents, queue consumers and topic publishers fromagent:0.6.4/queue-consumer:0.6.4toghcr.io/brf-tech/runr/agent:0.6.5andqueue-consumer:0.6.5; each rolls once. A region that pulls through a mirror of your own needs these two images there before the upgrade (Order of operations). - A mirror also needs
ghcr.io/brf-tech/runr/image-upload:1.1.1. The upload receiver and the transfer agent of the uploads and organization transfers started after the upgrade use it; nothing that runs is changed. Withimages.uploadImageororgTransfer.transferImageset, the regions keep the image named there: point it at 1.1.1 for the fix (images, orgTransfer). - Notifications older than 90 days are deleted. 0.6.5 adds the daily task
notification-retention(03:45). Its first run after the upgrade deletes every in-app notification older than 90 days, read or not, with the members' read state, and the notifications of accounts deleted earlier. To keep them longer, setnotifications.retentionDays(RUNR_NOTIFICATION_RETENTION_DAYS) before upgrading;0keeps them. The task runs in the central schema and, with multi-tenancy, in every organization's schema (notifications). Deleting an account now removes its notifications, centrally and in every organization; removing a member from an organization removes their notifications there only. - Shared notifications get a read and deleted state per member. The migration
notification_user_states(central, and with multi-tenancy the tenant migration 0110 in every organization's schema) only adds a table with its indexes and a foreign key tonotifications; no existing row changes. It is safe while 0.6.4 still serves requests: 0.6.4 never reads the table, and on PostgreSQL creating the foreign key briefly holds back writes tonotifications, not reads. A shared notification (one without a user, such as a resource threshold) that someone marked read or deleted before the upgrade, or on a 0.6.4 pod during the rollout, stays read or deleted for everyone; from 0.6.5, a member's mark read, Mark all as read, delete and Delete all apply to that member only. - Revoking the other sessions keeps the API tokens. Active Sessions and "Revoke All Other Sessions" cover sign-in sessions only (before, they also ended the user's CI, CLI and MCP client tokens);
DELETE /api/account/sessions/{id}answers 404 for an API token's id andDELETE /api/tokens/{id}for a sign-in session's id (Sign-in sessions and API tokens). - Every user lists and revokes their own API tokens and MCP clients (route rule
@own:tokens.manage), so Administration → API Tokens is in everyone's menu; creating a token or connecting an MCP client still needstokens.manage, now labelled "Create API tokens", and an API token limited to some permissions must still carry it to list or delete the other tokens (Organization).GET /api/tokensaddsmcp_client. - The API reference serves a document built with the API image.
/api/docs.jsonlists the endpoints of every module, also of those the installation has turned off, and names its server relative to the host (/api): a client generated from it takes the installation's address as its base. It answers with an ETag andCache-Control: public, max-age=300. Six operationIds changed, so an SDK generated from the document renames these methods:workflowRun.indexandworkflowRun.indexForWorkflow(both wereworkflows.workflowRun.index_0),workflow.app(wasworkflows.workflow),modelService.invoke(wasai.modelService),billingSettings.showandbillingSettings.update(weresettings.showandmodules.billing.settings.update) (0.6.4 → 0.6.5 has the table). GET /api/brandingaddsfeatures.auth_providers; nothing is removed. The sign-in page reads it before it asks for SSO providers (UI build flags).- The UI images are larger (150 MB for linux/amd64, 124 MB for
ui:0.6.4): they carry a Brotli and a gzip copy of every text file, which Caddy sends as they are. A UI image built from source builds onghcr.io/brf-tech/runr/reqs/node:22-alpine(vue-i18n 11 requires Node.js 22). - Back to 0.6.4: a plain
helm rollback(orhelm upgradewith the 0.6.4 chart where only one package version is kept) on the same database; there is no migration to undo: thenotification_user_statestable stays, and 0.6.4 ignores it. Notifications that the retention task or an account deletion removed stay removed. The region Job of the 0.6.4 chart moves the region images back to 0.6.4, and uploads and transfers started after the rollback use image-upload 1.1.0 again. - Terraform provider 0.6.5: its resources and data sources are the ones of 0.6.4.
From 0.6.3, upgrade straight to 0.6.5 and read 0.6.3 → 0.6.4 as well: 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.4 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.5 (2026-11-04)
Upgrade notes
One new database migration, notification_user_states (each member's read and deleted state of the
shared notifications), run by the pre-upgrade migration Job in the central schema and, with
multi-tenancy, in every organization's schema (tenant migration 0110). It only adds a table, is safe
while 0.6.4 still serves requests, and a rollback to 0.6.4 ignores it; a shared notification read or
deleted before the upgrade stays so for everyone. One new Helm value, notifications.retentionDays
(default 90): values of 0.6.4, --reuse-values included, keep working and render it as 90 (0.6.4 →
0.6.5 in upgrade.md). 0.6.5 adds the daily task notification-retention
(03:45). Its first run after the upgrade deletes every in-app notification older than 90 days, read
or not, with the members' read state, and the notifications of accounts deleted earlier. To keep
them longer, set notifications.retentionDays (RUNR_NOTIFICATION_RETENTION_DAYS) before
upgrading; 0 keeps them. Deleting an account removes its notifications in every organization.
Regions that pull through a mirror need ghcr.io/brf-tech/runr/image-upload:1.1.1 there, next to
the agent and queue-consumer images of 0.6.5: the uploads and organization transfers started after
the upgrade use it. An installation that sets images.uploadImage or orgTransfer.transferImage
keeps the image named there. Gateway-auth, supply-chain and the Spin shim keep their versions.
Revoking the other sessions keeps the API tokens; every user lists and revokes their own API tokens
and MCP clients, creating one still needs tokens.manage ("Create API tokens"). GET /api/branding
adds features.auth_providers and GET /api/tokens adds mcp_client. The API reference
(/api/docs, /api/docs.json) serves a document built with the API image: it lists the endpoints
of every module, also of those turned off, names its server relative to the host (/api), and six
operationIds changed (workflowRun.index, workflowRun.indexForWorkflow, workflow.app,
modelService.invoke, billingSettings.show, billingSettings.update): regenerate an SDK made
from it. The UI images carry pre-compressed copies of their files (150 MB for linux/amd64, 124 MB in
0.6.4). A UI image built from source builds on reqs/node:22-alpine.
Security
- Dependency updates for published advisories (the Audit workflow had failed since 0.6.3). The
console's code editor sanitizes with DOMPurify 3.4.17 (GHSA-cg2g-xh64-v4q7, critical;
GHSA-mrv2-3pqr-j5jr, GHSA-p98j-92pf-mc4p, GHSA-6688-9rhm-gjv2, GHSA-c6gr-qvv4-5v3f): monaco-editor
0.57.0 ships its own copy, DOMPurify 3.4.15, which the build now replaces with the dompurify
package (vue/build/monacoDompurifyPlugin.js; the build fails if a newer Monaco moves its copy).
The console takes vue-i18n 11.4.18 (GHSA-83rm-6c8r-g728, GHSA-8rc2-428q-7ww3: no fixed 9.x or
10.x exists; the UI image builds on Node.js 22, which vue-i18n 11 requires) and follow-redirects
1.16.2 (GHSA-mrwp-f3q8-3g9p, used by axios). The API takes symfony/mime 7.4.22 (CVE-2026-45070,
e-mail header injection through MIME parameter names) with symfony/polyfill-mbstring 1.43.3.
Build tooling: Vite 6.4.5 (GHSA-8g5g-mxqh-grgj) and Vitest 4.1.12 (GHSA-qxg6-89mg-rqv8,
GHSA-xp26-3454-mjgp).npm audit --omit=devreports nothing; the dev tooling keeps two moderate
advisories of minimatch and glob that eslint 10 and js-beautify (of @vue/test-utils) do not take
the fixed majors of yet.
Fixed
-
Notifications no longer pile up forever. Nothing ever deleted an in-app notification: the
shared ones, the read ones and the ones users had deleted (a soft delete) stayed in the
database for good, with every member's read state of the shared ones. The new daily task
notification-retention(03:45) deletes the notifications created more than 90 days ago —
read or not, deleted or not, with their members' state — in the central schema and in every
organization's schema, in chunks of 1,000 rows. The retention is the new setting
RUNR_NOTIFICATION_RETENTION_DAYS(Helm valuenotifications.retentionDays, default90,
0keeps every notification; helm-values.md). The first
run after the upgrade deletes every notification older than the retention. -
A deleted account's notifications go with it. Deleting an account, by its user or by an
administrator, left the user's notifications and their read and deleted state of the shared
ones behind; it now deletes them in the central schema and, in the multi-tenant edition, in
every organization the account belonged to. Removing a member from an organization deletes
their notifications there. The dailynotification-retentiontask also removes what
deletions before this release left behind, whatever the retention. -
Revoking the other sessions no longer ends the user's API tokens. Account settings → Active
Sessions listed every token of the user, API tokens included, and "Revoke All Other Sessions"
(POST /api/account/sessions/revoke-all) deleted them all but the current one: signing out the
other browsers also broke the user's CI, CLI (runr-cli@<host>) and MCP client tokens. The
session routes now list and revoke sign-in sessions only (the tokens namedapiand
invitation-accept, which API tokens cannot take since 0.5.5): revoking one by an API token's
id answers 404, revoking all others ends every other sign-in session and keeps the API tokens.
API tokens are listed and deleted under Administration → API Tokens only;DELETE /api/tokens/{id}
answers 404 for a sign-in session's id. What the other paths end is unchanged and now tested:
signing out ends the token of the request, a password change the other sign-in sessions,
disabling the account every token but the current one, deleting it every token; two-factor
changes and a frozen account's refused requests end none. Disabling the account now also signs
out the other browsers at once (session.revoked), as a password change does, and Active
Sessions no longer lists a session that ended (past its expiry or the session lifetime, as the
sign-in check counts it) until the daily cleanup removed it. Signing out a cookie session (no
stored token) answered 500; it now ends the web session. Listing and revoking one's own API
tokens and connected MCP clients no longer needs a role permission (route rule
@own:tokens.manage: a limited API token must still carrytokens.manage); creating a token
still needstokens.manage. Administration → API Tokens is shown to every user, without the
create form for a role that lacks it; in an organization of the multi-tenant edition such a
member lists their own tokens only. Thetokens.managelabel reads "Create API tokens". The
tokens of connected MCP clients stay on that list, now labelled "MCP client" (mcp_clientin
GET /api/tokens). No data migration. -
One member's Mark all as read or Delete all no longer changes the other members'
notifications. A shared notification (one without a user: a resource threshold, the result of a
job nobody started) had one read state and one deletion for everyone, so when a member marked it
read, deleted it, or used Mark all as read or Delete all, it was read or gone for every member of
the organization. Each member now reads and deletes shared notifications for themselves (the new
tablenotification_user_states, in the central schema and in every organization's schema): the
list, the unread badge and/api/notifications/unread-countare per member. A user's own
notifications keep their state as before. A shared notification someone read or deleted before
the upgrade stays read or deleted for everyone. -
The API reference opens again.
/api/docs.jsonand the reference page/api/docsgenerated
the OpenAPI document on each request, which takes longer than a request may run: on every
install they ended in a 500 at the 30 s limit, or never loaded. The API image now builds the
document once (php artisan runr:api-docs, a stage ofapi/Dockerfile.prod) and both serve that
file,/api/docs.jsonwith an ETag andCache-Control: public, max-age=300. It documents the
endpoints of every module (Tenancy, AuthProvider, Ticket, Billing), also of those an install has
turned off, and names its server relative to the host (/api). The page also loaded a viewer
script the image never had: the image now carries the Scalar viewer (1.75.1, checked against its
SHA-256), without its AI chat, MCP generator and telemetry. A checkout without the built file
(development) still generates the document per request
(development.md). -
Every operation of the API reference is in one group with a proper name, has a one-line
summary and an operationId of its own (Projects > Deployments, Regions > Install, Sandboxes >
Files, …). An operation whose controller names its group was also in a second one named after the
controller class (Images and Image, Bindings and Binding), most others were in such a class name
(AdminSupportTicket, GitWebhook), and the Sandbox API's operations were in pieces of their
controllers' descriptions ("TTL", "delete", "activity log (docs/sandbox-api.md)."). The billing
module's group also took the core's Settings endpoints. Most operations had no summary, one that
restated their method and path, or a paragraph; each now says in one line what it does ("List the
project's workflows"), the rest is its description. The two lists of workflow runs shared the
operationIdworkflows.workflowRun.index_0, which OpenAPI requires to be unique. These
operationIds changed (SDK generators name their methods after them):workflowRun.indexand
workflowRun.indexForWorkflow,workflow.app(wasworkflows.workflow),modelService.invoke
(wasai.modelService),billingSettings.showandbillingSettings.update(weresettings.show
andmodules.billing.settings.update). The webhooks, Git callbacks, invitations and public status
and developer pages no longer show a required token. The image build and CI fail when an
operation lacks a summary, an operationId of its own or a group (php artisan runr:api-docs --check). -
The console's files are no longer compressed on each request. The UI image's Caddy compressed
every response as it sent it: the 4.9 MB main bundle took 4.4 s with zstd on demo.runr.sh. The
build now puts a Brotli (quality 11) and a gzip (-9) copy next to every text file above 1 KiB,
and Caddy sends those as they are (file_server { precompressed br gzip }), Brotli first: the
main bundle goes out as 1.0 MB. A client that takes only zstd gets it compressed on the fly as
before (every browser that takes zstd takes Brotli). Cache-Control and the other headers are
unchanged; what has no copy (small files,branding-defaults.js, which the container writes at
start) is still compressed on the fly, now gzip first. Both UI images (ui,ui-mt) are built
this way, their build stage on the build host's platform. -
The transfer agent could report a failed pull without its reason, or a pull without its
result (image-upload 1.1.1). It wrote its.failedand.donemarkers by creating the file,
then writing it, and its own watcher could read one in between, empty. Markers are now renamed
into place; an empty.failedof a tool script (a shell redirection creates the file before the
reason is in it) counts only when it is still empty at the next look. Regions that pull through
a mirror needghcr.io/brf-tech/runr/image-upload:1.1.1. -
The sign-in page no longer asks for SSO providers without the AuthProvider module, which
left a 404 ofGET /api/auth-providers/discoverin the browser console on every visit. It asks
only when the console has the module's screens and the API reports the module on
(features.auth_providersofGET /api/branding, new). -
The CAPTCHA widget is light on the sign-in and sign-up cards, which are light in both
console themes; elsewhere (the invitation page) it follows the console's theme instead of the
browser's, and is drawn again when the theme changes. -
The console no longer shows message keys while it starts. The messages of the modules every
image has (branding and onboarding, bot protection, images, sandboxes, …) came in only after the
optional modules had loaded, so in the multi-tenant image the onboarding wizard of a new
organization showed its keys (whiteLabel.onboarding.title, …) for a moment. They are now in
before the first render.
