Skip to content

Releases

v0.1.1

Choose a tag to compare

@github-actions github-actions released this 03 Sep 11:55

Verify before installing. The checksums below are signed with
sigstore - keyless, so there is no certificate to trust and
no key for anyone to steal. Both commands run where you downloaded the files:

sha256sum --check --ignore-missing SHA256SUMS

cosign verify-blob \
  --bundle SHA256SUMS.sigstore.json \
  --certificate-identity-regexp '^https://github[.]com/dinesh-ad/truestill/[.]github/workflows/release[.]yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  SHA256SUMS

The second proves the checksums were produced by this repository's own release workflow.
cosign is at https://github.com/sigstore/cosign. On Windows use certutil -hashfile <file> SHA256 in place of sha256sum.

Windows. These builds are not code-signed (DECISIONS.md D9), so Windows shows a
SmartScreen warning - when you launch the installer, before anything is installed,
and again the first time you run the app from the portable zip. Choose More info
then Run anyway. The warning is reputation-based per file and clears as downloads
accrue.

macOS is not published. Gatekeeper refuses unsigned applications outright rather
than warning, so an unsigned build would be one most people could not open. Windows and
Linux only for now.

Linux. No gate of any kind - the .deb installs and runs.

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 30 Aug 15:08

Do not use 0.1.0 to organize. Take 0.1.1.

These downloads shipped without the file that draws the Organize
screen's results. The screen looks fine and Look inside runs, but the
preview, the completion card and every error message on that screen
never appear, so a run tells you nothing about what it did. The other
six screens are unaffected, and nothing on disk is at risk from this:
it is a screen that stays blank, not a run that does the wrong thing.
0.1.1 fixes it and now checks for that file before publishing.


Verify before installing. The checksums below are signed with
sigstore - keyless, so there is no certificate to trust and
no key for anyone to steal. Both commands run where you downloaded the files:

sha256sum --check --ignore-missing SHA256SUMS

cosign verify-blob \
  --bundle SHA256SUMS.sigstore.json \
  --certificate-identity-regexp '^https://github[.]com/dinesh-ad/truestill/[.]github/workflows/release[.]yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  SHA256SUMS

The second proves the checksums were produced by this repository's own release workflow.
cosign is at https://github.com/sigstore/cosign. On Windows use certutil -hashfile <file> SHA256 in place of sha256sum.

Windows. These builds are not code-signed (DECISIONS.md D9), so Windows shows a
SmartScreen warning - when you launch the installer, before anything is installed,
and again the first time you run the app from the portable zip. Choose More info
then Run anyway. The warning is reputation-based per file and clears as downloads
accrue.

macOS is not published. Gatekeeper refuses unsigned applications outright rather
than warning, so an unsigned build would be one most people could not open. Windows and
Linux only for now.

Linux. No gate of any kind - the .deb installs and runs.