-
ForgeFlow 0.10.4
StableForgeFlow quality gate / quality (push) Canceled after 0sJens released this
2026-08-01 13:11:43 +00:00 | 59 commits to main since this releaseForgeFlow 0.10.4
Permanent packaged updater handshake repair
- Binary and source update helpers now use a Windows PowerShell 5.1-compatible atomic status replacement with a real temporary backup path.
- A deterministic overwrite fallback preserves lifecycle reporting on filesystems that do not implement atomic replacement.
- The binary helper exposes a side-effect-free handshake-only verification mode exercised by the real Windows PowerShell executable during tests.
- existing installations with the defective helper require this one-time installer upgrade; every subsequent packaged update uses the repaired helper automatically.
- Startup failures retain request-scoped status and helper-log evidence instead of collapsing into an unexplained exit-code message.
Downloads
-
ForgeFlow 0.10.3
StableForgeFlow quality gate / quality (push) Canceled after 0s2026-08-01 12:38:05 +00:00 | 60 commits to main since this releaseForgeFlow 0.10.3
Responsive large workspaces
- Repository monitoring checks up to four local working trees concurrently while retaining overlap protection and per-repository pause controls.
- Global search, repository filtering and the command palette debounce full interface renders during rapid typing.
- Commit-message input updates readiness and action controls in place, preserving focus and cursor responsiveness.
- Interactive project illustrations and diff atmosphere effects perform at most one layout update per animation frame.
Git Validator reliability
- Git Validator and every long repository tab now retain an explicit vertical scroll owner across compact, desktop and wide layouts.
- Standard, Strict and Production policies correctly treat configured warning severities as blockers; Minimal remains error-only.
- Documented suppressions no longer reduce the hygiene score or remain counted as active blockers.
- Repair requests are rescanned immediately before preview or execution, preventing stale or forged fixes.
Verification
- Full quality gate, coverage thresholds and all responsive browser scenarios pass for this release.
Downloads
-
ForgeFlow 0.10.2
StableForgeFlow quality gate / quality (push) Canceled after 0s2026-07-29 23:08:00 +00:00 | 65 commits to main since this releaseForgeFlow 0.10.2
Packaged updater origin repair
- Gitea release assets that expose an internal HTTP
ROOT_URLare safely rewritten to ForgeFlow's configured public HTTPS Gitea origin. - Authentication remains same-origin: the Gitea token is never forwarded to an internal address, CDN or unrelated redirect target.
- Published Windows executables are still validated as PE files and against their release SHA-256 sidecars before staging.
- The live authenticated updater acceptance downloads the exact published installer and proves its byte count and SHA-256 digest.
Downloads
- Gitea release assets that expose an internal HTTP
-
ForgeFlow 0.10.1
StableForgeFlow quality gate / quality (push) Canceled after 0s2026-07-29 22:52:27 +00:00 | 66 commits to main since this releaseForgeFlow 0.10.1
Reliable certificate-free updates
- Windows installer and portable releases are supported without paid signing services.
- Packaged updates remain protected by exact Gitea release assets, PE validation and SHA-256 verification before staging and immediately before replacement.
- Old ForgeFlow versions are pruned from
distafter each successful build.
Deployment inventory correctness
- Repository matching is case-insensitive, so
Jens/Repoandjens/reporefresh the same deployment profile. - Running repository workloads are linked conservatively; third-party DockerMan applications remain visible as external monitoring-only workloads instead of generating hundreds of false repository problems.
- Historical and stopped duplicate definitions no longer require repetitive manual review.
- Shadowed automatic profiles are retired only after a recovery snapshot and a stable reviewed reconciliation plan.
- Live runtime, container health and commit evidence are refreshed before readiness is reported.
Server pull verification
- Existing running repository workloads can receive repository-scoped read-only deploy keys without changing containers.
- The audit command supports compact inventory, reconciliation and access evidence for operational verification.
- Release acceptance no longer assumes an external Authenticode certificate while retaining checksum, provenance and SBOM checks.
Downloads
-
ForgeFlow 0.10.0 Stable
2026-07-28 06:27:26 +00:00 | 87 commits to main since this releaseForgeFlow 0.10.0
ForgeFlow 0.10.0 makes existing Unraid workloads substantially easier and safer to adopt, verify and deploy.
Deployment discovery and verification
- Automatic discovery links unique running server workloads to their matching Gitea repositories while excluding unrelated infrastructure and stale release folders.
- Deployment cards preserve the last verified live commit and compare it with the current Gitea branch, even when a container was updated outside ForgeFlow.
- Existing Compose project names, files, services, remote folders and DockerMan metadata are adopted from server truth instead of guessed or overwritten.
Safe Server pull
- Server pull is now the recommended deployment route and fetches the exact requested commit from Gitea.
- Each repository receives its own repository-scoped read-only deploy key; ForgeFlow never installs the desktop Gitea token on Unraid.
- Gitea SSH host fingerprints are pinned and checked before trust is changed and before every pull.
- Fetch, archive, checksum, Compose validation, activation and rollback remain exact-commit and transactional.
- Direct copy remains available when server-side Git access is undesirable, and monitoring-only links cannot deploy accidentally.
Git hygiene
- Git Validator now also checks
.gitattributes,.editorconfig, dependency lockfiles and a Gitea Actions workflow. - Safe repairs create reviewable files without committing or pushing them automatically.
- Existing identity, upstream, synchronization, branch-protection, documentation, secret-path and oversized-file checks remain available in one scored view.
Interface and reliability
- The deployment workspace now emphasizes repository, container, environment and live-versus-Gitea evidence, with a focused animated project illustration and clearer server inventory.
- Large unrelated server inventories are summarized instead of producing dozens of indistinguishable cards.
- Connection validation consistently opens the same encrypted Electron profile as the installed app.
- Obsolete ForgeFlow artifacts are removed from
distafter every successful packaged build.
No container was restarted or replaced during automatic discovery. Deployments still require a successful preflight and an explicit user action.
Downloads
-
ForgeFlow 0.9.0 Stable
2026-07-27 21:33:43 +00:00 | 89 commits to main since this releaseForgeFlow 0.9.0
ForgeFlow 0.9.0 changes Unraid deployments from a Git-checkout-first workflow into a server-inventory-first workflow.
Existing installations are now visible
Server Inventory collects a safe, selected subset of Docker, Compose and DockerMan metadata for both running and stopped containers. It recognizes Compose project names, working directories, active Compose files and services, mounts, ports, runtime state, image provenance and existing DockerMan templates. Environment values and other container secrets are not collected.
Exact repository provenance may be linked automatically. Name similarity is never treated as proof: uncertain workloads remain visible as suggestions and can be linked through the new manual wizard. The saved link preserves the workload identity rather than depending on the disposable container ID.
Push bundle is the new default
New SSH/Unraid profiles use Push bundle. ForgeFlow creates a tar archive from the exact local Git commit, calculates its SHA-256 digest and uploads it over the already trusted desktop-to-Unraid SSH connection. Unraid therefore does not need a Git client, Gitea host-key entry or Gitea private key for this mode.
The server verifies the checksum and archive paths, rejects symlink payloads, preserves configured runtime paths, updates only ForgeFlow-managed files and validates the merged Compose model before starting services. The active SHA and managed-file manifest are promoted atomically only after the expected services are running. Failure restoration keeps the previous deployment truth and restores overwritten files and Compose metadata.
Server-side Git remains available as an explicit mode. Its Gitea access check is now reported separately from desktop SSH and Docker/Compose capabilities. Monitor only links an existing workload without granting ForgeFlow permission to deploy it.
Safer adoption
Adopted workloads retain their existing Compose project, Compose files and service set. ForgeFlow no longer overrides their image or container name in the metadata overlay. Existing DockerMan templates are left untouched; generated templates are managed only for explicitly generated Compose profiles.
--force-recreateand--remove-orphansare opt-in rather than defaults.A deployment lock records the live shell process, and an old lock is removed only when it is sufficiently old and its owner no longer runs. Deployment output truncation now fails explicitly instead of allowing ForgeFlow to interpret an incomplete inventory or command result.
Downloads
-
ForgeFlow 0.8.9 Stable
2026-07-26 03:24:42 +00:00 | 92 commits to main since this releaseForgeFlow 0.8.9
ForgeFlow 0.8.9 introduces Git Validator, a dedicated repository assurance
workspace that checks whether practical Git and Gitea best practices are being
followed.The validator produces a weighted score with evidence for repository identity,
upstream tracking, working-tree state, effective commit identity, safe local
synchronization defaults, default-branch and force-push protection, README and
gitignore hygiene, tracked secret-shaped filenames and oversized tracked files.Every repair is deliberately bounded. Origin alignment and repository-local
fetch/pull/autostash safeguards can be applied as safe fixes. Creating default
branch protection or a recommended.gitignorerequires explicit confirmation.
The generated.gitignoreremains uncommitted for review, and secret/history
findings are never modified automatically.The new workspace includes grouped findings, an assurance score, safe-fix
batching, audit events, interactive project illustration and responsive premium
layouts for light and dark themes.Downloads
-
ForgeFlow 0.8.8 Stable
2026-07-26 02:51:02 +00:00 | 93 commits to main since this releaseForgeFlow 0.8.8
ForgeFlow 0.8.8 fixes the HTTP 404 returned while downloading packaged updates
from the configured Gitea server.The server's API requires release attachments to be addressed using both the
immutable release ID and attachment ID. ForgeFlow now uses that exact
release-scoped endpoint for the executable and its checksum file.Strict same-origin token protection and SHA-256 verification remain unchanged.
Install 0.8.8 manually when upgrading from 0.8.7 because the affected download
code runs before the corrected updater can be installed. Future packaged
updates can again be completed from inside ForgeFlow.Downloads
-
ForgeFlow 0.8.7 Stable
2026-07-26 02:22:23 +00:00 | 94 commits to main since this releaseForgeFlow 0.8.7
ForgeFlow 0.8.7 automatically discovers applications already running on every
configured and trusted Unraid server. It inventories server-side Git checkouts,
Docker Compose metadata, bind mounts, container identity and image provenance,
then links each workload to a Gitea repository only when the evidence produces
one unambiguous match.Uniquely matched workloads are added to Deployments automatically, even when
they were originally deployed outside ForgeFlow. Every refresh resolves the
configured branch directly on Gitea and compares its full commit SHA with the
live server version. A deployment is reported as in order when the SHAs match,
the container is running and Docker health is not failing.Containers without a server-side Git checkout can also be discovered when the
image exposes standard OCI source/revision labels or ForgeFlow provenance
labels. New ForgeFlow deployments now write repository, branch and exact commit
labels so future discovery remains deterministic.Ambiguous or weak matches are intentionally left unlinked for manual review.
Server inventory is read-only; automatic adoption changes only ForgeFlow's local
configuration.Downloads
-
ForgeFlow 0.8.6 Stable
2026-07-26 02:07:19 +00:00 | 95 commits to main since this releaseForgeFlow 0.8.6
ForgeFlow 0.8.6 gives the changes workspace a richer, more purposeful visual
identity. Unused diff-canvas space now presents a contextual animated code map
that reflects the selected file type and its additions and removals.Subtle travelling signals, floating status nodes and pointer-responsive depth
bring the canvas to life while keeping every diff line fully readable. Dense
diffs automatically reduce the illustration's presence, and narrow panes hide
it entirely when there is no useful room.The changed-file list also gains clearer state chips, stronger active-file
hierarchy and refined hover feedback. All effects support light and dark themes
and respect the operating system's reduced-motion preference.Downloads