Skip to main content
Private preview. fremforge is in private preview — invited customers only. Content is still subject to change. Request access →
Reference
Changelog

Changelog

This page documents user-visible changes to fremforge: new features, breaking changes (rare), and the weekly runner-image rebuild manifest. Entries are added in reverse-chronological order.

For the full firehose of operational changes, anchor cron runs, sub-processor announcements, edge-rule adjustments, see the trust page and the status page.

Conventions

Each release entry has four blocks:

  • Date, the day the change went live to customers (UTC).
  • Surface, runners, admin, api, ssh, docs, pricing, trust, etc., the customer-facing area affected.
  • Change, what changed, in language a customer recognises.
  • Action required, what (if anything) the customer must do. Omitted when none.

Breaking changes carry a ⚠ breaking tag. Customers with active subscriptions also receive an email a minimum of 14 days before any breaking change ships.

Entries

2026-05-08, Hosted CI runners online

  • Surface: runners, actions
  • Change: fremforge’s hosted Forgejo Actions runners are now live. Workflows targeting runs-on: fremforge execute inside our runner-base image (Alpine 3.22 + bash, GNU coreutils, git + git-lfs, build-essentials, Node 22 LTS, jq, yq, gitleaks, trivy, kaniko, shellcheck, shfmt). See docs.frem.sh/build/actions/runner-image/ for the full tooling list and how to install language toolchains via standard setup-* actions. The image rebuilds weekly with a Trivy CVE gate; per-build manifests publish to the runner-image manifests linked below.
  • Action required: None for now. The first sandbox-tenant onboarding flow uses the full path. Existing self-hosted (BYO) runner setups continue to work unchanged.

2026-05-06, Initial publication

  • Surface: trust, infra
  • Change: First publication of this changelog at docs.frem.sh/reference/changelog/. Referenced from docs/runners/ for the weekly runner-image manifest. Pre-launch operations changes from before this date are not back-published.
  • Action required: None. Bookmark this page or subscribe to its RSS feed (link below) once Hugo renders one.

Subscribing

This page emits an RSS feed at https://docs.frem.sh/reference/changelog/index.xml once the Hugo build ships. Add it to your reader of choice. We don’t send a separate changelog email, the security mailing list is the only push channel, and it covers sub-processor changes (per DPA §10.2), security advisories, and upcoming breaking changes.

Runner image manifests

Each weekly hosted-runner image rebuild publishes its manifest under /changelog/runner-images/, that sub-section is auto-generated by the rebuild pipeline rather than hand-written, so the manifest never goes stale relative to the SWR digest. The manifest includes:

  • runner-base SWR digest + base image (Alpine major.minor)
  • Pre-installed tool versions (node, npm, jq, yq, git, gitleaks, trivy, kaniko, shellcheck, shfmt)
  • CVE scan summary (HIGH/CRITICAL fail with --ignore-unfixed; MEDIUM disclosed)
  • CycloneDX SBOM (linked from each manifest entry)
  • Diff vs previous week’s manifest

The pipeline shipped 2026-05-08; the bootstrap image (runner-base:20260508-142738-bootstrap) was the first push, its manifest entry will be backfilled before the first weekly auto-rebuild lands. Subsequent rebuilds (Mon 06:00 UTC) auto-publish.

Why docs.frem.sh/changelog and not www.frem.sh/changelog

The audience for release notes is operators and developers using fremforge, the same audience already reading docs.frem.sh. Marketing copy lives at www.frem.sh. Keeping the changelog colocated with the docs site means: (1) one Hugo build, one navigation surface; (2) the runner-image manifest sub-page can be auto-generated by the rebuild pipeline writing to the same content tree; (3) deep-links from runbooks and docs pages stay same-origin.

Related

Last updated: 2026-05-06.