Unexpected commit with git log --all

[nativerv]

Are such commits expected to be here? It's not shown with plain git log, but:

$ git log --pretty=oneline --all
f4c2e140652c28997296aed48862fb27301cd927 "$(git config transcrypt.crypt-dir 2>/dev/null || printf %s/crypt ""$(git rev-parse --git-dir)"")"/transcrypt textconv
<rest omitted>

[jmurty]

Hi, no that doesn't seem right. Which version of transcrypt are you using?

[nativerv]

Hi, no that doesn't seem right. Which version of transcrypt are you using?

Well, i've tested it now on transcrypt 2.3.0 from nixpkgs 88195a94f390381c6afcdaa933c2f6ff93959cb4 by adding and committing a file and there's no bad commit/stash/whatever that is in the log. (Only this warning btw on git add -f secrets/test.txt, which probably deserves it's own ticket:)

*** WARNING : deprecated key derivation used.
Using -iter or -pbkdf2 would be better.

Last time this commit got to my .git was Sep 2 2024, around which i was probably on 2.2.3 from nixpkgs 6e99f2a27d600612004fbd2c3282d614bfee6421.
I don't however remember any more specifics. The issue is probably fixed, but you can doublecheck if you want.
To be clear, the working branch does not have the commit. It's a stash or something.