Repository navigation
Releases: Flow-Steward/flow-steward-app
Release list
v0.9.9
Flow Steward 0.9.9. Immutable source: 493cbad.
Docker Hub is available and verified: all seven official image roles, linux/amd64 and linux/arm64, at docker.io/flowsteward/*:0.9.9. Index, platform, config digests and embedded release identity were checked against the successful native builds.
GHCR is currently unavailable for publication (permission_denied: write_package). This release deliberately uses the complete verified Docker Hub fallback; it does not claim both registries are published.
Focused acceptance: 97 backend and 113 frontend checks passed for this revision. Full Tier 3 and SonarQube were not rerun, as explicitly requested by the user. Original build and acceptance run: https://github.com/Flow-Steward/flow-steward-app/actions/runs/41607722552.
Use the normal release upgrade --target-version 0.9.9 command. This version includes database migrations; create a verified backup and follow the migration instructions before resuming work.
0.9.7 — AI-agent access, extension update notices
AI agents can now work with Flow Steward directly. Through MCP an agent can create and edit agents and skills, check and repair workflows, and follow, restart and read the results of jobs; errors keep their domain codes, so the agent knows what to fix. Creating or renaming an agent, skill or workflow with an ID or a display name that is already taken is refused with the existing matches, instead of silently making a duplicate.
Settings → Account → AI agents walks through connecting Claude Code, Codex, Cursor, Gemini CLI, Claude.ai, Cowork or ChatGPT with the Operator or Developer skill package: it issues one access token per attempt with a chosen preset and expiry, shows whether the token has been used, and revokes it. Cloud AI apps connect through OAuth sign-in and consent instead of a token; an administrator can turn this off in Settings → Security, and connected apps are listed next to personal tokens.
Installed extensions now show when a newer release is available in the catalog, on the Installed tab, on the extension page and as a counter in the menu, with a link to its release notes and a warning when the new release does not run on this server.
Security: a token that expires can no longer create a token that outlives it.
Existing installations get the new OAuth tables through the regular upgrade. Native AMD64 and ARM64 images are published to GHCR and Docker Hub. The Operator and Developer skill packages are attached to this release.
0.9.6 — complete Scalable upgrades and security fixes
A Scalable flow-steward release upgrade now completes: the upgrade no longer mistakes its own one-off runner container for a second CLI container, which left 0.9.5 upgrades marked pending after the services were already updated.
Security fixes from an independent audit: a personal access token without admin:all can no longer create one that has it; workflow exports carry only the guardrails of projects the exporter may see and mask credential defaults inside nested schemas; project listings respect a token's workflow allowlist; resetting the private-address setting reliably restores its default; boolean provider-trigger conditions are enforced; the text padding action has a width limit; malformed extension error codes no longer break failure reports. CSV and XLSX exports neutralize spreadsheet formulas in text cells. pyasn1 is updated to 0.6.5.
Native AMD64 and ARM64 images are published to GHCR and Docker Hub.
0.9.5 — reliable Scalable upgrades and a quieter UI
Upgrading a Scalable installation with flow-steward release upgrade no longer needs manual repair: Compose now gets the host path of the installation state from inside the CLI container, so the storage configuration and every service's runtime state are mounted correctly; the upgrade also replaces the CLI container, and services keep their Python bytecode cache inside the container.
The interface no longer darkens the screen or blocks clicks while it refreshes data already on screen, and pages whose data does not change on their own (workflows, extensions, registry, datasets, projects, settings, trash) stop polling the server. Live views (dashboard, running jobs, monitoring) keep refreshing quietly. Native AMD64 and ARM64 images are published to GHCR and Docker Hub.
0.9.4 — workflow bundles, agent own I/O, host settings
Workflow export now carries agents, skills, contracts and guardrails, and an import resolves template connections to the right extension and project.
Adds a text preview in Job Details, editable agent-own inputs and outputs, extension events that start workflows (with hub_signature webhooks for Meta), and one name for every host setting in the CLI and installer.
Includes fixes for extension polling and provider triggers that could stop, workflow import and mapping checks, and registry categories. Native AMD64 and ARM64 images are published to GHCR and Docker Hub.
0.9.3 — standard date tools and QA fixes
Adds standard date and time tools, including deterministic parsing, formatting, timezone conversion, arithmetic, and interval operations.
Includes workflow authoring, Hook, clipboard, registry, approval, and artifact presentation fixes. Native AMD64 and ARM64 images are published to GHCR and Docker Hub.
Flow Steward 0.9.2
Flow Steward 0.9.2 is a testing release ahead of 1.0.
What changed
- Official Postgres image. The database image (PostgreSQL 17 with pgvector and Apache AGE) is now published as
flow-steward-postgresforlinux/amd64andlinux/arm64on GHCR (ghcr.io/flow-steward) and Docker Hub (docker.io/flowsteward). A fresh install of this release tag pulls it with the other digest-pinned images instead of building it locally, which removes the slowest local build from a first install. - Both installation profiles (Compact and Scalable) use the same Postgres image.
- Updating an existing install keeps your data: the image is built from the same Dockerfile and base, and the database container is recreated on the same volume.
- Releases before 0.9.2 still use the locally built Postgres image.
Install
git clone --branch v0.9.2 https://github.com/Flow-Steward/flow-steward-app.git flow-steward
cd flow-steward
./install.shDocumentation: https://docs.flowsteward.org
Feedback
Please report problems in Issues and attach the System Diagnostics report (Monitoring → Download diagnostics, or ./flow-steward reports diagnostics).
Flow Steward 0.9.1
Flow Steward 0.9.1 is a testing release ahead of 1.0.
What changed
- Install from official images. A fresh install of this release tag now pulls the published, digest-pinned images instead of building them locally. Images are published for
linux/amd64andlinux/arm64on GHCR (ghcr.io/flow-steward) and Docker Hub (docker.io/flowsteward); the installer uses the first complete registry. - Any other checkout (a branch or a commit with local changes) still builds from source, as before.
- If the release images cannot be found, the installer stops with
release_images_unavailableand says why; it never falls back to a source build silently.
Install
git clone --branch v0.9.1 https://github.com/Flow-Steward/flow-steward-app.git flow-steward
cd flow-steward
./install.shDocumentation: https://docs.flowsteward.org
Feedback
Please report problems in Issues and attach the System Diagnostics report (Monitoring → Download diagnostics, or ./flow-steward reports diagnostics).
Flow Steward 0.9.0
Flow Steward 0.9.0 is our first testing release ahead of 1.0. We are sharing it with early testers to collect feedback, identify issues and improve everyday workflows before the 1.0 release.
What is included
- A self-hosted workflow builder with connected steps, groups and For each loops.
- Workflow execution through declared triggers, webhooks, REST API, MCP and schedules.
- Human approvals, wait steps, execution history and workflow version management.
- Extensions Marketplace, workflow templates and MCP server catalogs.
- Compact and Scalable installation profiles.
- The current batch of bug fixes and refreshed installation and operation guides.
Install this testing release
Install Docker with Linux containers and Docker Compose v2 first, then run a full Git clone:
git clone --branch v0.9.0 https://github.com/Flow-Steward/flow-steward-app.git flow-steward
cd flow-steward
./install.sh
./flow-steward status
./flow-steward doctorThe installer builds this pinned checkout locally in Docker. This pre-release does not provide a verified multi-platform production image set and is not offered by the stable-release updater. Core ships without bundled extensions; install the integrations you need from the in-product Marketplace.
Follow the README and installation guide.
Feedback
Please open an issue with what you tried, the expected result, the actual result and steps to reproduce. Attach the System Diagnostics report from Monitoring → Download diagnostics when reporting a bug. Use the private channel in SECURITY.md for security reports.
Release history
This repository starts with one clean initial commit for 0.9.0. Previous development history has not been imported. Version 1.0 will follow after feedback and further stabilization.