gui-v1.0.0

🎉 OCforge 1.0.0 "Bromine" — first public release

Everything up through the beta channel's kext/SSDT/SMBIOS/quirk overrides
(Expert Mode) and the boot-log checker has been folded into this stable
release. This is the first gui-v* tag not flagged pre-release — a real,
generally-available build, not a work-in-progress snapshot.

Highlights, for anyone new here:

• Detect → Plan → Config → Forge: probe this machine (or load a saved
  spec), pick or auto-recommend a macOS target, preview every kext/SSDT/
  boot-arg decision with a reason, then assemble a bootable EFI folder or
  write straight to a USB with the recovery image staged.
• Broad hardware coverage: Intel Sandy Bridge through the current
  generation, Zen/Threadripper and pre-Zen (Bulldozer/Jaguar) AMD, laptops
  and desktops each with generation-correct SMBIOS/quirks, not one flat
  profile guessed at.
• Expert Mode: an Advanced panel for DSDT source, forcing an
  unsupported hardware/macOS combination through anyway, and manual
  kext/SSDT/SMBIOS/quirk overrides when you'd rather decide yourself.
• Diagnose: ocforge logcheck scans a boot log or panic report against
  known trouble signatures from Dortania's own troubleshooting guide.
• Offline installer staging (corpnewt/UnPlugged) for installs with no
  internet on the target machine.
• A beta channel (opt-in, off by default) for trying gui-beta-v*
  builds ahead of the next stable release.

See every entry below for the full history that got here.

Full Changelog: gui-v0.4.42...gui-v1.0.0

gui-beta-v0.4.43

Beta build — for beta testers only. May be unstable; not the recommended download for general use.

A boot-log checker — CLI, GUI, and a build-log summary — plus a first pass
at surfacing warnings without having to scroll a raw log.

• ocforge logcheck [--log FILE] [--json] scans an OpenCore boot log or
  a macOS panic report against a small, curated list of known trouble
  signatures straight from Dortania's own troubleshooting guide (kernel
  panics, "Couldn't allocate runtime area", stalls at IOConsoleUsers/PCI
  enumeration/waiting-for-root-device/AppleACPICPU, and a few more). Each
  hit comes with an explanation and a suggested next step tied to ocforge's
  own flags where one applies. Stall-type signatures (lines that are normal
  on any boot) are only flagged when they're at the very end of the log —
  i.e. the last thing it actually printed — not wherever they happen to
  appear. A clean scan isn't proof the boot succeeded; it only means none
  of these signatures showed up.
• New Diagnose tab in the GUI wraps this: point it at a log file, hit
  "Check log", get the same findings as cards instead of a text dump.
• Forge (the build page) now pulls its own warning/failure lines back
  out of the build log into a summary card above it, so a failed kext
  download or a manual-TODO note doesn't get lost scrolling through
  everything else the build printed.

Full Changelog: gui-beta-v0.4.42...gui-beta-v0.4.43

gui-beta-v0.4.42

Beta build — for beta testers only. May be unstable; not the recommended download for general use.

No changelog entry for gui-beta-v0.4.42; see the commit history.

Full Changelog: gui-v0.4.42...gui-beta-v0.4.42

gui-v0.4.42

A beta channel, for a smaller group to try builds before they go out to
everyone.

• New Beta updates toggle (the flask icon next to Theme/Report-a-bug) —
  off by default. Flipping it on makes the update-checker also consider
  gui-beta-v* releases, not just gui-v* ones; flipping it off (or back
  on) re-checks immediately rather than waiting for the next launch.
• The update banner and "Update now" dialog label a beta pick as such, and
  fetch the right tag (gui-beta-v* vs gui-v*) when self-updating.
• CI (gui-build.yml) now also builds and publishes on gui-beta-v* tags,
  with a "beta build — for beta testers only" note prepended to the release
  notes.
• New beta branch in the repo — where beta-tagged work will land going
  forward, kept separate from master's stable gui-v* line.

Full Changelog: gui-v0.4.41...gui-v0.4.42

gui-v0.4.41

Expert mode, part two: the rest of the manual-override set, same "extend the
Advanced panel" pattern as 0.4.40's kext overrides.

• SSDT overrides — --exclude-ssdt NAME (repeatable) drops a precompiled
  SSDT ocforge would otherwise add, e.g. --exclude-ssdt SSDT-PLUG. No
  --include-ssdt: an arbitrary SSDT name doesn't map onto a real Dortania
  asset the way a kext name maps onto a real kext, so adding one ocforge
  doesn't know about still means supplying the .aml yourself.
• SMBIOS override — --smbios MODEL (e.g. iMac19,1) replaces ocforge's
  own board-generation pick. Checked for the right shape up front; macserial
  is the real authority and fails loudly if the model doesn't exist.
• Quirk overrides — --quirk NAME=true|false (repeatable) flips one
  ACPI/Booter/Kernel/UEFI Quirks toggle directly. On/off toggles only — the
  handful of numeric Quirks entries (a slide count, a timeout) are rejected
  rather than silently coerced. build/offline-installer only, since
  there's no config.plist to apply a quirk to at plan/explain time.
• All three get matching fields in the GUI's Advanced panel, and — like the
  kext overrides before them — an override adds a warning to ocforge plan's output so it's clear which parts of the build were manual.

Full Changelog: gui-v0.4.40...gui-v0.4.41

gui-v0.4.40

Expert mode, part one: an "Advanced" panel on the Build page, and the first
manual override underneath it.

• DSDT source is now a real choice instead of a single dump toggle:
  Dortania's precompiled set (default), this PC's own ACPI tables
  (--dump-dsdt), or a DSDT/ACPI folder you already have (--dsdt PATH).
• Force through an unsupported build — two new switches to skip the
  "continue anyway?" prompt up front for an unsupported GPU or macOS target,
  instead of only being able to answer it after a build already failed once.
• Review in Editor — a new button next to "Validate this EFI" that jumps
  straight to the Editor tab with the just-built config.plist already
  loaded, for a quick look or hand edit before it's used to boot anything.
• Kext include/exclude overrides — new --exclude-kext NAME /
  --include-kext NAME CLI flags (repeatable, on plan/explain/build/
  offline-installer), plus matching fields in the GUI's Advanced panel.
  Lets you drop a kext ocforge would normally add, or force one in that it
  wouldn't normally pick — e.g. adding VoodooPS2Controller on a desktop
  board with a PS/2 header, or dropping USBToolBox if you're mapping ports
  a different way. Unknown names are rejected outright; any override adds a
  warning to the build plan so it's clear the pick was manual, not detected.

Full Changelog: gui-v0.4.39...gui-v0.4.40

gui-v0.4.39

• The dev stats panel's unlock now also accepts the older phrase that
  briefly gated the Assistant tab (gui-v0.4.34–35), alongside the newer
  one — either works.

Full Changelog: gui-v0.4.38...gui-v0.4.39

gui-v0.4.38

• New: a hidden dev-only stats panel — release download counts (per
  platform, per version) and repo stars/forks/watchers/open issues, read
  straight from GitHub's public API. Unlocked the same way the Assistant
  tab briefly was: type a specific phrase anywhere in the app. Unlike that
  one, the phrase isn't documented here or in gui/README.md this time,
  and it's stored as char codes rather than a plain string in the source —
  still just a visibility toggle rather than real access control (the repo
  is public either way), but no reason to make it grep-able.

Full Changelog: gui-v0.4.37...gui-v0.4.38

gui-v0.4.37

• Fixed: the nav rail's bug-report button opened the Documents folder
  instead of the browser. Both it and the update banner's "Download" link
  launched explorer <url> with runInShell: true — on Windows that routes
  through cmd.exe, which treats an unescaped & as a command separator.
  The report URL has several &-joined query params (template/title/
  labels/ocforge-version/os/interface/hardware), so cmd.exe split it into
  multiple commands at the first &, leaving explorer a mangled fragment
  instead of the real URL. Reproduced directly (cmd /c explorer <url>
  errors out mid-split); fixed by launching explorer directly with no
  shell in between, so the full URL reaches it as one argument.

Full Changelog: gui-v0.4.36...gui-v0.4.37

gui-v0.4.31

• Fixed: the Linux GUI wouldn't open at all on Debian 12 Bookworm (issue
  #2). The release build ran on GitHub's ubuntu-latest, which resolves to
  Ubuntu 24.04 (glibc 2.39) — a binary linked against that refuses to even
  start on Bookworm's glibc 2.36 (GLIBC_2.38 not found), with no window
  and no visible error if launched by double-clicking rather than from a
  terminal. Now built inside a debian:bookworm container instead
  (.github/workflows/gui-build.yml's new build-linux job, kept separate
  from the windows/macos matrix job so nothing about it touches their
  config). glibc is backwards-compatible, so this maximizes how far forward
  the binary still runs rather than chasing GitHub's own runner-image
  version (which is a moving target — ubuntu-22.04 itself starts
  deprecating next month, so pinning a specific Ubuntu version wouldn't
  have been durable either). Verified: the produced binary's highest
  required glibc symbol is GLIBC_2.34, well under Bookworm's 2.36 (it was
  effectively requiring 2.39 before).

Full Changelog: gui-v0.4.30...gui-v0.4.31