Download Latest Version OpenEstate v0.9.1 -- Cheque Queue Validation Fix source code.zip (2.5 MB)
Home / v0.9.1
Name Modified Size InfoDownloads / Week
Parent folder
OpenEstate v0.9.1 -- Cheque Queue Validation Fix source code.tar.gz 2026-11-04 1.9 MB
OpenEstate v0.9.1 -- Cheque Queue Validation Fix source code.zip 2026-11-04 2.5 MB
README.md 2026-11-04 3.3 kB
Totals: 3 Items   4.5 MB 2

A small fix release on top of v0.9.0. The v0.9.1 tag identifies the released commit. Nothing else changed: no new features, no migrations.

What was fixed

GET /api/v1/receipts/cheque-queue returned HTTP 500 when its status filter was not one of the defined cheque statuses (for example ?status=PENDING, a lowercase value, a value with a trailing space, or status given twice). It now returns HTTP 400 with a validation message naming the field (status: …).

The Cheque Queue screen only ever sends valid values, so people using the app as normal were not affected; the 500 came from hand-made or scripted requests. It was a read, so nothing was changed or exposed. The problem was already present in v0.8.5; it was found during the v0.9.0 upgrade rehearsal.

Technical details

  • The status query parameter is now validated with zod before the handler runs. Before, the raw value reached the database query, and the database library's rejection of an unknown value surfaced as a 500.
  • The five cheque clearance statuses still work: NOT_APPLICABLE, RECEIVED, DEPOSITED, CLEARED and BOUNCED.
  • A missing or empty status still shows the default queue (received and deposited cheques that haven't been reversed).
  • Sign-in, the cheque permission, company isolation and the BOUNCED tab (which lists reversed receipts) work exactly as before.

Upgrading from v0.9.0

From the server's source folder, with the release tag:

:::bash
cd /opt/openestate-src/deploy/native && sudo ./upgrade-native.sh --ref v0.9.1

Use the tag or a full commit SHA, never a branch name, and keep the automatic pre-upgrade backup on (don't pass --no-backup). Afterwards curl -s http://127.0.0.1:3000/api/v1/health reports "version":"0.9.1".

Upgrading from an older version: read the v0.9.0 release notes first, which cover that release's migrations, permission and backup changes; this release adds nothing to them.

Compatibility

Compared with v0.9.0:

  • no new database migrations;
  • no new environment variables;
  • no role or permission changes;
  • no new infrastructure requirements;
  • no change to financial calculations or ledger behaviour.

The only application change is the validation in the receipt controller.

How it was checked

  • Pull request [#81]: a new HTTP-level test (5 tests, real PostgreSQL, the app's own validation) checks that unknown values get 400 and never reach the query, and that missing, empty and valid statuses, the BOUNCED tab, company isolation, the permission and sign-in are unchanged. In local runs it failed on the v0.9.0 code (500), passed with the fix, and failed again when the v0.9.0 code was put back. In CI it passed 5/5 on the pull request (run 41756215289, all 10 jobs successful).
  • CI on master after the merge (run 41757757822) passed all 10 jobs: lint, typecheck, unit tests and build; integration tests (including the new test); Playwright end to end; native install; native upgrade; and the five upgrades from earlier releases.

Known limitations

Everything listed under "Known limitations" in the v0.9.0 release notes still applies, except the cheque-queue 500, which this release fixes. The other open items in docs/todo.md are unchanged.

Source: README.md, updated 2026-11-04