v0.1.9

FaceForge v0.1.9 (2026-01-15)

This is a patch release focused on Desktop bundling reliability and significant improvements to the documentation generation pipeline (HTML/PDF).

Summary

• Desktop packaging: Ensures the official SeaweedFS weed.exe is staged during release builds (so installers ship a real binary, not a placeholder).
• Docs pipeline: Improves the config-driven update-docs.ps1 workflow and makes PDF generation more robust.
• Repo hygiene: Consolidates documentation under docs/, improves styling/assets, and removes leftover version-pinned links.

Upgrade Notes

• No manual configuration changes are expected for this update.

Known Issues

• No new issues have been identified in this release. If you hit something, please file a GitHub issue with logs from FACEFORGE_HOME/logs/.

v0.1.8

FaceForge v0.1.8

Patch release focused on Desktop orchestration quality-of-life and maintainer/dev workflow polish.

Highlights

• Desktop orchestration improvements: auto-restart behavior and a “minimize on exit” setting (plus UI updates).
• PowerShell scripts: richer comment-based help and auto-generated scripts documentation.
• Versioning hygiene: aligns version metadata across manifests + tracked lockfiles for repeatable builds.

Upgrade Notes

• No manual configuration changes are expected for this update.
• Core API surface remains versioned under /v1/... (no API version bump).

Known Issues

• No new issues identified. If you hit something, please file an issue and include logs from FACEFORGE_HOME/logs/.

Changelog (high level)

• Enhance PowerShell scripts + README generation
• Desktop settings: auto-restart + minimize-on-exit
• Version consistency updates for packaging/build automation

(Full details in RELEASE_NOTES.md.)

v0.1.7

FaceForge v0.1.7 Release Notes

This is a patch release focused on documentation/packaging polish and keeping version metadata consistent across Core and Desktop.

Summary

• Docs output: Auto-generates HTML/PDF versions of README docs.
• README accuracy: Updates FACEFORGE_HOME directory structure and config path details.
• Versioning: Keeps version strings aligned across the repo for bundling and release automation.

v0.1.6

FaceForge v0.1.6 Release Notes

This is a patch release focused on stability and operational polish across Core and Desktop. It includes improvements to how the local filesystem layout is structured, reduces logging edge-cases during reload, and tightens a couple of first-run/wizard flows.

Summary

• Core layout: Introduces dedicated runtime and tools directories to keep the FaceForge home clean and predictable.
• Logging: Refines logging setup to reduce duplicate-handler behavior and keep rotation reliable.
• Desktop wizard/UI: Makes first-run settings persistence more robust and aligns the settings payload structure.
• Automation: Improves non-interactive build behavior for CI and scripted usage.

What Changed

Core

• New FaceForgePaths fields: Adds run_dir and tools_dir and threads them through layout/config/ports handling.
• Logging initialization cleanup: Refactors the log handler setup to avoid duplicate handlers on reload, and keeps output consistent.

Desktop

• First-run robustness: Ensures the temporary directory exists before saving wizard settings.
• Settings payload consistency: Updates the UI-side payload structure to match what the desktop side expects.

Build & Developer Experience

• Non-interactive builds: Updates scripts/build-core.ps1 to avoid confirmation prompts when running unattended.
• Dependency metadata hygiene: Keeps Tauri desktop lockfile version metadata consistent.

Upgrade Notes

• On next start, Core will create new subfolders under FACEFORGE_HOME (notably run/ and tools/) if they do not already exist.
• No manual configuration changes are expected for this update.

Known Issues

• No new issues have been identified in this release. If you hit something, please file a GitHub issue with logs from FACEFORGE_HOME/logs/.

---

v0.1.5

FaceForge v0.1.5

This release focuses on improving Desktop orchestration and UI workflows, and tightening up Core’s local-first runtime behavior (logging, path/layout, and port coordination).

Highlights

• Desktop orchestrator is more resilient when locating and launching bundled tools (Core + supporting utilities).
• Desktop UI adds clearer settings + log access and improves overall layout/styling.
• Core adds rotating file logging and refines its local runtime folder/file conventions.

Desktop (Tauri)

• Improved tool path resolution and startup stability in the orchestrator.
• Updated ports coordination / file structure expectations between Desktop and Core.
• UI updates: settings and log viewing flows, plus styling/layout polish.

Core (FastAPI)

• Logging: Core now writes to ${FACEFORGE_HOME}/logs/core.log using size-based rotation (configurable max size + archive count).
• Runtime temp files: asset upload staging now uses ${FACEFORGE_HOME}/tmp (instead of mixing temp artifacts into other directories).
• System info: reported path details were adjusted to reflect the updated layout.

Dev / Maintenance

• Added scripts/set-version.ps1 to bump versions consistently across Core + Desktop + Tauri config.
• Minor housekeeping updates (e.g., .gitignore tweaks).

Upgrade notes (important)

• Runtime ports file location changed:
  • Previous: ${FACEFORGE_HOME}/run/ports.json (and/or ${FACEFORGE_HOME}/runtime/ports.json in older docs)
  • Now: ${FACEFORGE_HOME}/config/ports.json
    If you have scripts/tools writing ports, update them to the new location.
• Core home layout expectations shifted toward ${FACEFORGE_HOME}/tmp for transient files.

Known issues

• None reported in this release.

---

For a full list of changes, please refer to the git log.

Full Changelog: v0.1.4...v0.1.5

v0.1.4

FaceForge v0.1.4

What's New

This release focuses on improving the Desktop experience and documentation.

• Desktop UI: Added new status and log controls, and improved the layout of the Settings screen.
• System: Updated Tauri permissions and window configurations for better stability.
• Documentation: Clarified installation steps and First Run setup in the User Guide.

Downloads & Installation

We provide two different ways to run FaceForge depending on your needs.

1. FaceForge Desktop Installer (Recommended)

Download: faceforge_desktop_..._x64-setup.exe (or .msi)

This is the all-in-one package for most users. It includes:

• The Desktop App: manage the system, view logs, and launch the UI from your system tray.
• The Core API: automatically managed in the background.
• Tools: bundled dependencies so you don't need to install Python manually.

2. FaceForge Core API (Advanced)

Download: faceforge-core.zip (or .tar.gz)

Only download this if you are a developer or creating a custom headless setup.

• Contains only the Python API server.
• Does not include the Desktop management UI.
• Requires you to manage the process lifecycle manually.

---

For full setup instructions, please refer to the User Guide.

v0.1.3

Fixes

• Version Consistency: The build pipeline now automatically injects the release version (from the Git tag) into the application configuration files (pyproject.toml, auri.conf.json) before building. This ensures the resulting MSI and executables report the correct version number.

v0.1.2

Fixes

• CI Build Robustness: patches scripts/build-core.ps1 to correctly handle PyInstaller output paths and file locking on Windows CI environments.
• Diagnostics: Adds detailed logging of dist/ folder contents to assist with future debugging.

Context

Previous releases failed to attach assets because the build script could not locate the generated executable in the CI environment. This release includes the necessary path resolution logic.

v0.1.1

Fixes

• Fixed a Desktop startup failure where the UI could show a scary “Tauri event API not available” modal and become unresponsive.

  • Enabled the Tauri global JS API (window.__TAURI__) for the no-bundler Desktop UI.

• Removed unexpected/empty console windows on Windows:

  • Desktop now uses the Windows GUI subsystem in release builds (no console window).
  • Core/Seaweed child processes are spawned with CREATE_NO_WINDOW to avoid popping terminals.

• Cleaned up build output:

  • Removed Rust dead_code warnings by deleting an unused field and deserializing core.json into typed config structs.

UX

• Replaced browser-style modal alerts with a gentle, in-app dismissible error banner in the Desktop UI.
  • Wizard validation and startup failures now render as friendly in-app messaging.

Notes

• If you previously installed a broken build, reinstall using this release’s installer to pick up the Desktop fixes.

v0.1.0

FaceForge v0.1.0

First end-user Windows release of FaceForge Desktop (Tauri) bundling a local FaceForge Core server. This is a “boring core” foundation: local-first storage + stable API + basic UI workflows, designed to be extended by plugins later.

Downloads (Windows x64)

• FaceForge Desktop installer: FaceForge_0.1.0_x64_en-US.msi (recommended)
• Core server (advanced): faceforge-core.exe
• Checksums: SHA256SUMS.txt

What’s included

• Desktop-managed local bundle (no Docker):

  • First-run wizard to choose FACEFORGE_HOME and localhost ports
  • Tray-based lifecycle controls (start/stop services, open UI)
  • Bundles the Core server executable

• Core API server (localhost-only by default):

  • Binds to 127.0.0.1
  • Token required for non-health endpoints (install token)
  • OpenAPI available at /docs and /redoc
  • Persists metadata in SQLite under FACEFORGE_HOME
  • Serves the built-in Web UI

• Core Web UI (MVP):

  • Login page to enter the install token
  • Basic flows to create/browse entities, upload/link assets, view jobs, and manage plugins/config

Quick start (end users)

1. Install and run FaceForge Desktop (.msi)
2. Complete the first-run wizard (pick FACEFORGE_HOME)
3. Use “Open UI” from Desktop (or visit the localhost URL it shows)
4. Paste the install token at the login page

Notes / limitations

• This release does not include face recognition, embeddings, LoRA training, graph visualization, or deep third-party integrations. Those are intended as plugins.
• Core is intended to remain a stable platform: CRUD + storage + jobs/logs + plugin surface.
• Current release assets are Windows x64.