1.7.0

Released: TBD

Highlights

• New itemPriceRange query returns the min/max unit price across the catalog so the frontend can bound a price-range filter/slider without loading every item.

Added

• itemPriceRange(includeArchived: Boolean! = false): ItemPriceRange! — a single aggregate query (MIN/MAX over items.unit_price) returning a nullable { minPrice, maxPrice }. Archived items are excluded unless includeArchived is set. See Item Price Range.

Changed

• None.

Fixed

• None.

Migrations

• None. Read-only query over the existing items.unit_price column.

Frontend impact

• Call itemPriceRange once when opening the items list / filter panel to seed a price slider's min/max bounds; mirror your archived toggle into includeArchived so the bounds match the rows being filtered.
• minPrice / maxPrice are null when no items are in scope — render that as "no range available" rather than 0. Decimal comes back as a string.

Versioning notes

• MINOR bump (scripts/bump_version.py 1.7.0 --changelog-stub): new additive query and type, no breaking schema change. No deploy-order constraints.