Jens/ForgeFlow
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 24 Wiki Activity

updater fixed

Browse Source
This commit is contained in:
NuklearRabbit
2026-07-28 00:03:33 +02:00
parent f990c26014
commit d4d77c827a
18 changed files with 451 additions and 71 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/RELEASE_NOTES_0.9.0.md
+7
View File
@@ -21,3 +21,10 @@ The server verifies the checksum and archive paths, rejects symlink payloads, pr
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-recreate` and `--remove-orphans` are 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.
## Release publication correction
- The standard release publisher now publishes the validated source and matching Windows binary assets as one workflow.
- Added `Publish-Missing-Binary-Release.ps1` to repair a source-only Gitea release without reinstalling ForgeFlow manually.
- Binary publication now derives the repository owner, repository name and branch from ForgeFlow settings instead of hardcoding them.
- Missing-release errors now explain that packaged installations require both Windows executables and their SHA-256 sidecars.