In 1.32, hledger import FILE1 FILE2 ... seems to write all files' new transaction dates to all of the .latest* files. These are what import uses to remember which transactions it has already processed, so corrupting them will likely disrupt subsequent imports.
I consider this is a fairly serious regression, because it could be tedious to recover from if you do a lot of importing. Please avoid importing from multiple files at once with hledger-1.32; this will be fixed by 1.32.1.
Importing from one file at a time is safe (but it won't interleave transactions by date). Eg:
bad: hledger import a.csv b.csv
good: hledger import a.csv; hledger import b.csv
In 1.32,
hledger import FILE1 FILE2 ...seems to write all files' new transaction dates to all of the.latest*files. These are whatimportuses to remember which transactions it has already processed, so corrupting them will likely disrupt subsequent imports.I consider this is a fairly serious regression, because it could be tedious to recover from if you do a lot of importing. Please avoid importing from multiple files at once with hledger-1.32; this will be fixed by 1.32.1.
Importing from one file at a time is safe (but it won't interleave transactions by date). Eg:
bad: hledger import a.csv b.csv
good: hledger import a.csv; hledger import b.csv