Skip to content

repose 1.1.2

Choose a tag to compare

@NomadicDaddy NomadicDaddy released this 08 Nov 00:26
· 52 commits to main since this release

repose 1.1.2 is a maintenance release after 1.1.1. The app itself is unchanged. The release gate now catches a stale licence-notices file, tests check what Enter and Space do on every row you can reach with Tab, and 1.1.1's notes are corrected: Enter and Space already opened those rows. See CHANGELOG.md for the full list.

Downloads

  • repose.exe: Windows 11 x64. It needs Git 2.45 or later on PATH; no runtime is bundled or downloaded.
  • LICENSE (MIT), THIRD-PARTY-NOTICES.md and RUST-STD-COPYRIGHT.html: the licences of everything the executable contains.
  • SHA256SUMS: check your download with sha256sum -c SHA256SUMS, or in PowerShell compare (Get-FileHash repose.exe).Hash with its line.

The executable is unsigned, so Windows SmartScreen may warn about an unknown publisher.

To build from source instead, follow the README: pwsh scripts/qc.ps1 runs the gate and stages these same files, and pwsh scripts/install-user.ps1 installs them for the current user.

Development

  • The gate's licence-notices check now runs again when LICENSE or the vendored PowerShell grammar's LICENSE.txt changes. Before, editing only those files kept the step cached, so a stale THIRD-PARTY-NOTICES.md could pass the gate. The gate's self-test now checks that the step's input list covers every file the notices generator reads from the repository.
  • Tests pin what Enter and Space each do on every painted row that Tab reaches: a changed file opens its diff, a commit opens and closes, a commit's file opens that file's diff at the commit, a file-view line becomes the current line, and a repository becomes the selection without opening anything.

Correction to 1.1.1's notes

  • 1.1.1's known limitations said Enter doesn't open a changed file, commit or repository that Tab has reached. That was wrong: in 1.1.1 as released, Enter and Space already do what a click does on each of them, and the tests above pass on its unchanged app code.

Known limitations

  • Development: the other findings from 1.1.1's gate audit are still open for a later release. A gate step whose command can't start is recorded as a pass; the test step's cache key leaves out the machine's global git configuration; the warm test suite takes about 105 s; and pushes to the public repository run no checks. None of them changes what repose does.
  • Development: three of the 28 audits that apply have no current report, and no audit ran for this release, since it changes no app code.
  • scripts/install-user.ps1 has still been run only on the development machine; there is no clean-machine install record.

Startup is measured, not gated. This build's gate reported a median of about 1.4 s (runs of 1.5, 1.3 and 1.4 s) against a target of about 300 ms.