v0.13.2

Patch release: seven things that failed quietly

No new features. Every item here is something that went wrong without saying so.

An unknown address in the app rendered a blank page. There is now a not-found screen, so a
mistyped or stale link tells you what happened instead of showing nothing.

Searching for a name with a trailing space never matched. Name lookup in the query language
did not normalise whitespace, so a value pasted from elsewhere silently found nothing.

closedAt was returned by the API and documented nowhere. It is now in the OpenAPI spec and
in both API references.

A dialog was not announced as a dialog. The saved-filter dialog carried no modal semantics, so
screen readers did not present it as one.

Workspace owners and admins could not reach project Settings from the navigation rail, even
though they are allowed to use it.

Two build and release fixes worth knowing about

-Dfrontend.skip=true had never actually skipped the frontend build. The flag existed and did
nothing. It now works, which makes a backend-only build materially faster.

A release tag only reached production if it was pushed before the main build. Pushing the
branch first and the tag second meant the tag's build lost a race and the deploy chain broke. The
two now run as independent builds, which is why pushing a branch and a tag together produces two
builds rather than one.

---

Full Changelog: v0.13.1...v0.13.2