v1.0.1

What's new

Fixed

• A source self-update that fails to build now tells you why.

Internal

• A commit whose code imports a file you never staged is now refused before it is made.

Full notes

Fixed

• A source self-update that fails to build now tells you why. It reported the command instead
  of the reason. The updater threw the first line of the failed step's stderr, and for a
  bun run <script> failure the first line is the runner echoing the script it is about to run, so
  the dashboard showed $ node scripts/i18n-check.mjs && vue-tsc -b && vite build … and dropped
  the line that mattered a few rows further down. There was no second copy to fall back on: the
  updater builds a full per-step transcript, but only returns it when the update succeeds, so on a
  failure that one line was everything the user ever saw. It now keeps a bounded excerpt instead,
  skipping echoed commands and blank lines, preferring the lines that actually name a failure, and
  capping the result so it still reads as a notification. Reported in
  #24, where a broken main sent the rollback
  path a message that named the build command and nothing else.

Internal

• A commit whose code imports a file you never staged is now refused before it is made. Every
  gate in this repo read the working tree, where a newly written file is present whether or not it
  was ever git added, so lint, vue-tsc and the tests all passed on a commit that shipped the
  imports without their target. That is exactly what reached main on 2026-08-27: nineteen
  modules imported a sign-in-nudge helper and four *-variants files that were never committed,
  CI went red, and every source install that tried to self-update pulled a tree it could not build
  and rolled straight back. bun run check:imports resolves every relative and @/-aliased import
  against git's index, which is the same view a fresh clone gets, and it now runs in bun run check
  and in the pre-commit hook. Pointed at the offending commit it names all eighteen bad imports.

Install

Download the archive for your platform, extract it, and run the RepoYeti executable. It is a
single self-contained binary with the dashboard embedded; no install step, runtime, or sidecar
folder is required.

Platform	Asset
Linux (x64)	repoyeti-linux-x64.tar.gz
macOS (Apple silicon)	repoyeti-macos-arm64.tar.gz
Windows (x64)	repoyeti-windows-x64.zip
Windows (x64), with the system-tray toolkit	repoyeti-windows-x64-with-tray.zip

Compiled installs check GitHub Releases for updates and can install one from the dashboard (or
unattended, if you turn auto-update on); an update is only ever downloaded from this repository's
release assets and is verified against the published SHA256SUMS.txt before it is installed.
Source checkouts update in-app with git.
Full history: CHANGELOG.md

Full Changelog: v1.0.0...v1.0.1