github yoebuild/yoe v0.10.9

latest releases: v0.12.11, v0.12.10, v0.12.9...
one month ago
  • The TUI home header is easier to scan. Field names (Machine, Image, Query,
    Units, feed, Modules, Diagnostics) now render in plain white and their values
    in a bright accent color, so the data stands out from the labels at a glance.
    The search expression keeps its own coloring.
  • The TUI tab bar now sits on the top line next to [yoe]. The
    Machine/Image line and the build progress bar moved down a row, so the tabs
    are the first thing you see and the layout reads top-to-bottom.
  • Image builds now resolve virtual packages the same way every run. When
    several packages claimed the same virtual name (for example the providers of
    ifupdown-any), which one an image picked could change from one build to the
    next — so a package would drift in and out of the image, never staying cached
    and sometimes silently dropping out entirely. Resolution is now stable, so the
    same project always produces the same image and the cache holds.
  • The TUI Setup page can now adjust how many units build in parallel. A
    "Parallel builds" row sits below Machine and Image; press ←/→ (or h/l) to
    raise or lower the count. The choice is saved per project and used by the next
    build.
  • yoe build now builds independent units in parallel. Units whose
    dependencies are ready build concurrently instead of one at a time, so a full
    build finishes much faster. Up to 5 units build at once by default; change it
    with yoe build -j N, yoe config set parallel-builds N, or a
    parallel_builds line in local.star. The value is remembered per project,
    and yoe config show reports the one in effect.
  • u on the unit list toggles a unit's source between pin and dev mode. The
    same dev-mode prompt the detail view offers is now one keypress away from the
    list, acting on the unit under the cursor.
  • g / G jump to the top / bottom of the unit list. The keys were
    documented and worked on the Modules and Diagnostics tabs but were a no-op on
    the Units list itself; they now move the cursor there too.
  • Press ? on any TUI page for a keyboard cheat sheet. A centered help box
    lists every shortcut for the page you're on — navigation, build, inspect,
    filter, and the page-specific actions — with plain-language descriptions. When
    the list is taller than your terminal it scrolls (↑/↓, PgUp/PgDn, g/G) with
    the title and footer pinned; any other key dismisses it.
  • The TUI tab bar now uses zellij-style ribbon tabs. Each tab is a rounded
    colored banner sitting on a dark bar, with the active one highlighted in amber
    so the selected tab is obvious at a glance. Needs a powerline-patched terminal
    font to render the rounded tab edges.
  • yoe deploy now actually installs your dev-mode rebuilds. Iterating in
    dev mode and deploying used to silently drop your edits when the version
    number hadn't changed; deploy now reliably installs the rebuilt package.
    Restart the service from $ to pick up the new binary.
  • Dev mode can track an upstream branch automatically. A unit that declares
    both a tag and a branch flips to tracking that upstream branch when toggled
    into dev mode, so git pull, git push, and git log @{u}.. just work. The
    SRC column shows dev-mod when your checkout is past the pin, and the detail
    page shows how many commits ahead you are.
  • P pins the current HEAD with no picker. Pressing P records the
    checked-out tag (or commit SHA) as the unit's pin — no popup. Available in
    dev and dev-mod; a dirty tree prompts you to commit or stash first.
  • The SRC column shows pin for yoe-managed checkouts instead of leaving
    the cell blank, so you can tell at a glance which units are pinned.
  • Toggling dev → pin no longer looks like data loss. It resets the
    existing checkout to the pin in place and keeps the clone's full history
    instead of deleting the source tree and re-cloning on the next build.

To update, run: yoe update
Or download the binary for your architecture and place it in your PATH.
Note: Yoe is in heavy development. We recommend cleaning your build directory and re-creating projects (yoe init) with each new release.

Don't miss a new yoe release

NewReleases is sending notifications on new releases.