-
ForgeFlow 0.10.14
StableJens released this
2026-08-26 23:21:31 +00:00 | 41 commits to main since this releaseForgeFlow 0.10.14
Betere uitleg en een stabiele repositorywerkruimte
- Een nieuw doorzoekbaar Help center legt de belangrijkste workflows stap voor stap uit: eerste configuratie, changes en commits, Gitea workspace sync, deploymentdetectie, exacte serverdeployments, deploykeys, Git Validator, updates en diagnose.
- Contextuele help vanuit Gitea workspace sync opent onmiddellijk de relevante uitleg. De instructies maken expliciet wat ForgeFlow wijzigt, welke recovery ForgeFlow vooraf maakt en welke genegeerde runtimebestanden onaangeroerd blijven.
- De variabele repository context is samengebracht in één structurele zone. Quick actions, Local → Gitea → Server-status en gekoppelde deployments kunnen daardoor niet langer over de tabnavigatie of inhoud heen schuiven.
- Smalle werkruimtes gebruiken gecontroleerde horizontal tab navigation. Elke tab behoudt zijn volledige label en blijft bereikbaar zonder dat tekst door andere bedieningselementen loopt.
- Het Help center heeft een eigen premium, responsieve presentatie met categorieën, zoekresultaten, uitklapbare stappen, veiligheidsnotities en motion-safe projectillustratie.
Verificatie
- Volledige Node-testset en statische renderercontroles.
- 84 browser flows over dark/light, compact/desktop/wide, 100–150% schaal en reduced motion; de drie tijdens een semantische testaanpassing geraakte flows zijn daarna opnieuw groen uitgevoerd.
- Extra layoutasserties bewijzen dat repository context, tabs en tabinhoud elkaar niet overlappen bij 1024 × 768.
Downloads
-
ForgeFlow 0.10.13
Stable2026-08-26 22:42:47 +00:00 | 42 commits to main since this releaseForgeFlow 0.10.13
Veilige synchronisatie en aantoonbare release-integriteit
- Gitea workspace sync toont eerst de exacte additions, wijzigingen en deletions ten opzichte van de actuele upstream-SHA. Lokale commits worden beschermd in een recovery branch; staged, unstaged en untracked werk gaat naar een stash. Genegeerde runtimebestanden blijven onaangeroerd.
- Read-only achtergrondfetch houdt
aheadenbehindactueel zonder projectbestanden automatisch te wijzigen. Interval0schakelt netwerkfetch volledig uit. - Stale deployment links blokkeren niet langer de automatische, bewijsgebaseerde koppeling van de werkelijk draaiende vervangende workload.
- SSH-hostidentiteit wordt vóór het verzenden van credentials getoond en bij bevestiging exact vastgepind. Gitea-tokens vereisen HTTPS, behalve bij expliciete loopbackontwikkeling.
- Packaged updates vereisen een Ed25519-signed release manifest dat versie, tag, broncommit, artifactnaam, bytegrootte en SHA-256 bindt aan de ingebouwde publisher key. Hiervoor is geen betaald certificaat of Azure-dienst nodig.
- Diagnostische bundels exporteren geen ruwe remote output meer. Untracked diffs kunnen geen junction of symlink buiten de repository volgen en zijn begrensd op bestandsgrootte.
- De Git-toolsgrid behoudt nu de volledige inhoudshoogte binnen zijn eigen scrollvlak; workspace sync en troubleshooting overlappen niet meer. De demo bridge ondersteunt dezelfde recoveryflow als de desktopapp.
- Repositorymonitoring, deploymentpolling, Docker-inspect en SSH-verbindingen gebruiken begrensde paralleliteit en hergebruik waar dat veilig is.
Verificatie
- Volledige Node-testset, coveragepoort, architectuuraudit en dependency-audit.
- 72 browserflows over dark/light, compact/desktop/wide, 100–150% schaal en reduced motion.
- Windows installer en portable build, SHA-256-sidecars, provenance, CycloneDX-SBOM en ondertekend releasemanifest.
Downloads
-
ForgeFlow 0.10.12
StableForgeFlow quality gate / quality (push) Canceled after 0s2026-08-12 13:29:06 +00:00 | 50 commits to main since this releaseForgeFlow 0.10.12
Faster awareness with stricter deployment truth
- Repository refreshes are coalesced and briefly cache Gitea inventory and workspace discovery; a manual refresh remains fully forced and file changes arriving mid-refresh receive one trailing refresh.
- Server discovery reuses its Docker and Compose evidence for existing deployment profiles instead of opening a separate SSH session for every linked workload.
- Deployment status only claims exact Gitea commit parity after comparing a concrete branch SHA with the live server SHA; matching repository provenance alone is no longer sufficient.
- Container discovery uses batched Docker inspect with a safe per-container fallback when a container disappears during the scan.
- Active Gitea and SSH deployment polling uses bounded worker pools, improving multi-deployment latency without flooding external services.
- A stopped container can no longer be marked healthy because another process answers on its previous healthcheck port.
- Large repository and server-inventory lists use offscreen rendering containment to reduce layout and paint work.
- Inventory diagnostics now include scan and state-refresh durations, and Gitea bulk verification fails fast after a confirmed connectivity outage.
Downloads
-
ForgeFlow 0.10.11
StableForgeFlow quality gate / quality (push) Canceled after 0s2026-08-12 13:07:44 +00:00 | 51 commits to main since this releaseForgeFlow 0.10.11
Resilient repository refresh and consistent server pull
- Temporary Gitea list failures now use the in-session last-known-good repository inventory while local and server state continue to refresh. The UI clearly reports that remote data is stale.
- A closed output pipe from a detached parent process is no longer treated as a fatal desktop-app exception.
- Server pull, deploy-key verification, deployment, rollback and metadata now consistently prefer the verified linked checkout origin over a stale URL detected earlier on the server.
- Repository-scoped read-only deploy key checks remain fail-closed; a changed SSH host still requires explicit trust and access reconfiguration.
- The local browser test server now has a dedicated port and identity endpoint, preventing another localhost application from being mistaken for ForgeFlow.
- All 42 responsive browser flows pass across dark/light, compact/wide and reduced-motion configurations.
Downloads
-
ForgeFlow 0.10.10
StableForgeFlow quality gate / quality (push) Canceled after 0s2026-08-08 22:44:03 +00:00 | 52 commits to main since this releaseForgeFlow 0.10.10
Complete server-pull deployment repair
- Missing repository-scoped read-only deploy keys can be provisioned and verified from Unraid against the exact Gitea branch.
- A repository deployment root can now remain above its Compose working directory without breaking workload recognition or being overwritten by inventory refresh.
- Nested Compose files are preserved as repository-relative deployment paths, including Ludarium, Launchpad and ITWorx MCP Hub layouts.
- The Fix write access action now receives its permission-report parser correctly instead of reporting a false write-access failure.
- Server-pull preflight proves every required deployment file at the exact Gitea commit before any container activation starts.
- Runtime secrets remain in server-side
.envfiles and preserved appdata paths; no secret values are written to Git or diagnostic output.
Downloads
-
ForgeFlow 0.10.9
StableForgeFlow quality gate / quality (push) Canceled after 0s2026-08-08 21:59:44 +00:00 | 53 commits to main since this releaseForgeFlow 0.10.9
Reliable deployment inventory and preflight
- Unraid inventory now includes containers without healthchecks. Docker's complete JSON state is parsed safely instead of using a failing Go-template lookup.
- ForgeFlow is single-instance: opening it again focuses the existing window, preventing concurrent inventory scans and configuration writes.
- Server pull verifies required Compose files or the Dockerfile at the exact Gitea commit before any deployment operation starts.
- Server-pull verification now separates deploy-ready access from optional live-SHA and runtime-health evidence. A recoverable workload is no longer shown as blocked merely because parity is not yet provable.
- Deployment cards and audit output show concrete access blockers and non-blocking warnings instead of a generic incomplete result.
- All discovery, verification and preflight checks remain non-destructive; no containers are changed during these checks.
Downloads
-
ForgeFlow 0.10.8
StableForgeFlow quality gate / quality (push) Canceled after 0s2026-08-01 17:14:24 +00:00 | 54 commits to main since this releaseForgeFlow 0.10.8
Self-contained checksum verification
- Binary and source update helpers no longer depend on the optional PowerShell
Get-FileHashcmdlet. - Both helpers calculate checksums directly with the built-in .NET SHA-256 implementation.
- A real Windows regression test clears
PSModulePathand verifies the downloaded binary successfully in that minimal environment. - The helper still validates the exact published checksum before waiting for ForgeFlow to exit or changing installed files.
- This release retains the reliable non-detached launcher and server-to-repository recognition improvements from 0.10.6 and 0.10.7.
Downloads
- Binary and source update helpers no longer depend on the optional PowerShell
-
ForgeFlow 0.10.7
StableForgeFlow quality gate / quality (push) Canceled after 0s2026-08-01 17:00:18 +00:00 | 55 commits to main since this releaseForgeFlow 0.10.7
Reliable server-to-repository recognition
- Live, running workloads with one unique exact provenance or runtime-identity match are now linked automatically during normal server discovery.
- Automatic adoption creates only ForgeFlow configuration and observed state; it performs no container changes and never automatically removes stale profiles.
- Ambiguous, duplicate, external and monitoring-only workloads remain behind explicit Review & link confirmation.
- Every linked repository now displays an
Sdeployment badge with its profile count in the repository sidebar. - The repository release rail reports Linked with container and server identity even when a legacy workload has no verifiable live commit yet.
- DevRunbook-style DockerMan deployments therefore show the same linked relationship in Deployments, the repository sidebar and the repository workspace.
Downloads
-
ForgeFlow 0.10.6
StableForgeFlow quality gate / quality (push) Canceled after 0s2026-08-01 16:02:22 +00:00 | 56 commits to main since this releaseForgeFlow 0.10.6
Permanent Windows updater launch repair
- ForgeFlow no longer launches hidden PowerShell update helpers with Node's defective Windows
detachedprocess mode. - Binary and source updater processes remain hidden, are explicitly unreferenced after their verified handshake, and continue independently when ForgeFlow closes.
- A real Windows regression test now exercises the exact production Node spawn options instead of using a different process API.
- Startup is still fail-closed: ForgeFlow remains open unless the request-scoped helper status reaches
started. - Versions 0.10.4 and 0.10.5 need a one-time direct installation of 0.10.6 because their installed launcher cannot execute its own helper; updates after 0.10.6 use the repaired path.
Downloads
- ForgeFlow no longer launches hidden PowerShell update helpers with Node's defective Windows
-
ForgeFlow 0.10.5
StableForgeFlow quality gate / quality (push) Canceled after 0s2026-08-01 15:34:39 +00:00 | 57 commits to main since this releaseForgeFlow 0.10.5
Consistent repository and deployment links
- Every repository workspace now shows all configured deployment environments in a compact, directly actionable strip.
- The repository deployment tab includes every detected server workload linked to that repository, including its container, Compose identity, server and runtime state.
- A workload is only labelled linked when its repository and resolved profile both exist in the current ForgeFlow configuration.
- Stale or incomplete metadata is shown as Link unresolved and routed through explicit reconciliation instead of being presented as a healthy deployment.
- The global deployment inventory links directly to the correct repository deployment profile.
- Responsive browser coverage now verifies valid links, unresolved links, repository navigation and scrolling across dark/light and scaled layouts.
Downloads