Skip to content

Offline tests, CI, a changelog, and 0.4.0 - #8

Merged
jeremy-robotsson merged 1 commit into
mainfrom
chore/ci-tests-release
Oct 7, 2026
Merged

jeremy-robotsson merged 1 commit into
mainfrom
chore/ci-tests-release

Conversation

@jeremy-robotsson

Copy link
Copy Markdown
Member

Tests, CI, a changelog, and the 0.4.0 version for everything merged today (#5, #6, #7).

Tests (tests/run.sh, 64 checks, offline)

Each test runs in a throwaway HOME with the plugin linked where Omarchy puts it and stand-ins for the CLI (tests/fake-varlatch), curl (release API, /v1/meta, and assets from a local fake release), notify-send (answers --wait with a chosen action), and the omarchy commands. A real varlatch on PATH is filtered out, so "missing" means missing.

  • Manifest: valid, entry points exist, every schema key has a matching default (and enum/integer defaults are in range), and CHANGELOG.md has a section for the manifest's version.
  • Menu: connect / remembered server / VARLATCH_SERVER / missing CLI / live session rows, a glyph on every row, no rewrite when nothing changed, insertion after an entry with and without a trailing comma, rewriting in place while keeping user entries, device row from CLI 0.14.0 only, Update CLI row. Parsed with Omarchy's own stripJsonc rules, since a bad comma silently drops every menu extension.
  • Sign-in state: stale sign-ins (dead pid, other boot) forgotten, running ones kept, cancel of a stale one, the address form when no server is known, browser sign-in success and cancel.
  • Session length: --ttl for 24 and 8 hours; none for 0 or out of range.
  • Device sign-in: pending record and QR, approval after a pending round, denied, expired, refused start, cancel stopping the waiter's whole process group, the failure-to-device fallback, quiet takeover of a browser sign-in, CLI 0.13.0 refused with no buttons, expiry notification buttons.
  • Release check: the staleness and once-an-hour rules from Check for a release when the panel opens and the cache is stale #7, failure handling, checkUpdates off, a newer release available and notified once.
  • Install and update: installs the version the server runs, falls back to the latest when that version has no release CLI, declining installs nothing (exit 130), a checksum mismatch installs nothing, the update path replaces a release install, "up to date", and a source checkout is refused.

CI

.github/workflows/ci.yml on pull requests and pushes to main: Node.js 22, qrencode, shellcheck -S warning on the helper and the test scripts, then tests/run.sh. Actions are pinned by SHA, the same versions as varlatch/varlatch's workflows.

Release prep

  • CHANGELOG.md for 0.1.0 to 0.4.0 (earlier versions reconstructed from the manifest history).
  • manifest.json 0.4.0.
  • README: a Development section.

After this merges: tags v0.1.0 (1db0ccc), v0.2.0 (a676bc0), v0.3.0 (ba3c691), and a v0.4.0 GitHub release on the merge commit.

🤖 Generated with Claude Code

tests/run.sh checks the manifest and bin/varlatch-menu offline, each
test in a throwaway HOME with stand-ins for the CLI, curl, notify-send,
and the omarchy commands: the menu block (and that Omarchy's own JSONC
rules still parse it), stuck sign-ins, browser and device sign-in,
session length, the release check, and installing and updating the CLI
against a fake release. CI runs it with shellcheck on every pull request
and push to main, with actions pinned like varlatch/varlatch's.

CHANGELOG.md covers 0.1.0 to 0.4.0, and the manifest is 0.4.0.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@jeremy-robotsson
jeremy-robotsson merged commit 75e3e06 into main Oct 7, 2026
1 check passed
@jeremy-robotsson
jeremy-robotsson deleted the chore/ci-tests-release branch October 7, 2026 15:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant