0.2.2 — one file, and two things the API changed its mind about
A patch release with one correction, one parameter removed because the API
stopped accepting it, and one that should always have been required.
--env-file reads that file and no other
Its help has said "instead of looking for one" since the day the flag was
added, and the code read the named file after everything the search found -
so a setting the named file omitted was still answered by whatever was on the
machine, and a flag meant to make one client entry self-contained isolated
nothing.
One .env applies now: the highest-precedence file that exists, and the ones
below it are not read. Naming one skips the search entirely, which is what
--tools-file has always done for the policy file. A real environment
variable still beats the file, so a container keeps passing its transport
settings while the key lives in the mounted volume.
If your settings live in more than one file, put them in the one that wins.
The configuration interface now says so on the overview when it is editing a
.env that a server would not read.
create_voucher lost unchecked, because the API took it away
It worked on 2026-08-20 - vouchers created that day are still in the test
account saying so. On 2026-08-23 the same call is refused with
voucherStatus: invalid_value, across three voucher types. Nothing changed on
this side. A parameter that fails every time is worse than an absent one.
To record a receipt for review rather than book it, upload_file still files
the document as an unchecked purchase invoice.
create_voucher requires voucher_number
The API refuses a voucher without one, for all four types. It was optional, so
a call that omitted it spent a request to be told no.
Also
The package index now says Beta rather than Alpha. Twenty-five tools, each
exercised against a live account, two transports, a published image.
Every tool was called against a live account for this release: twenty-five of
twenty-five, no failures.
Upgrading from 0.2.1 is a pull or a reinstall.