Skip to content

Brick Work 0.6.0

Choose a tag to compare

@Ulef1005 Ulef1005 released this 29 Oct 07:38
· 492 commits to main since this release

The data-model release: the collection moves to schema 4.0 with a separate local catalogue, and the API to v2. Breaking: API v1 answers 410 except /api/v1/health; clients move to /api/v2 (API v2). A 0.5 collection is moved with brickwork migrate4 on a copy first (CLI); the 3.3 file is never changed.

  • Add says what each step does: numbered steps (Find and select, Review and add, Added), Select instead of Add to list on a search result (tap again to unselect), a bar that keeps Review in view, and an Add button that names where the items go. An item you already own or wish waits for Add another copy or Skip before Add is offered; before, Add was offered and the save failed. The wishlist options show only for the wishlist, and the item types wrap on a phone.
  • The site's API reference shows API v2 (#125).
  • An order keeps its currency when its document has no total (M.12, #114). An order e-mail has only line prices, so its order now stores EUR and the line prices show it instead of Currency not recorded; a total still needs its currency. Orders stored before get the currency from their raw document when the app starts. See Receive an order.
  • brickwork check and the Database page check that the two files belong together (M.12, #114): the collection is bound to the catalogue, every catalogue item and colour in the collection has the same born key there, every part list it names exists, and the digests agree. Each is a named check; a failure names the fix. API v2 /database/check is unchanged. See Back up and restore.
  • First run needs no key (M.12, #114). Sets on an empty install offers Download the catalogue (or Build from today's files when today's download is on disk, or Activate the catalogue for a file that is there but not switched on): one background job fetches Rebrickable's files, builds the catalogue, creates and seeds the collection file if it is missing, and activates and binds the catalogue. Add by number and Check Set Parts then work with no key. Keys became an optional step. See Settings and maintenance.
  • Part lists on the copy page and in Add (M.10 A). The Part list card names the list a copy uses and offers Switch with what changes and which marks will not carry over; a copy can ask for BrickLink's list and waits on the fetch (Cancel stops it); a copy built before a re-download says what changed; retired lines are kept in a collapsed note; a figure line names where its parts came from. The Add review has a Part list picker (with Use this for new copies of this set), warns about a part with no known picture, and offers Fetch from Rebrickable or Add as unidentified for a number not in the catalogue. A missing picture is a quiet dashed tile in light and dark. See Choose and switch a part list.
  • main is the 4.0 line: the app runs on the 4.0 store; API v1 answers 410 (except /api/v1/health) until API v2 (M.11).
  • The collection lists, the item page, the wish, lot and purchase-place pages and the jump search run on the 4.0 store. An item page is /collection/item/<id>; the old number URLs redirect to it. Screens show the Rebrickable number first with the BrickLink number beside it where it differs, a BrickLink-only item marked, and an unidentified item by its name; search takes both numbers. Conditions and completeness are words on every screen.
  • Check Set Parts and the collection's writes run on the 4.0 store: a check keeps its answers by part line, so switching a copy to another part list keeps a check in progress; checks in progress before 4.0 start again. Editing, archiving, restoring and Undo (one receipt per save), own photos and captions, new part lots and the loose-stock merge on edit work as before. A figure's own parts are checked at /workbench/check-parts/<copy>/figure/<line>. Own photos are served at /manage/images/<id>.
  • The Workbench runs on the 4.0 store: Part Picker, Matcher (Give and Take), Found it, instruction booklets, Part to Inventory (the page, its save and Undo), Storage with its history, and the printable lists with their CSV. A move writes one receipt and a stock_transfer row naming it. Matching is by item: a part, a figure, or a set's booklet or box meets the loose stock of the same item and colour, and an item still marked to check is matched like any other (the Needs a check list is gone). Instruction booklets are added by the numbers of booklets you already hold or the BrickLink item list names. Photo recognition in Part to Inventory comes back with Identify.
  • Pictures, prices and keys run on the 4.0 store. The import job fetches a picture (from the Rebrickable catalogue, BrickLink and the Rebrickable API, in the order of the setting; parts try the catalogue first), Brickset metadata and retail price, and BrickLink prices for every colour a part is held in; calls are counted per source and day. An item with no BrickLink number ends the price step as unidentified instead of failing. The Prices screen works by item id and its Update buttons queue the same step. Fetch from Rebrickable now makes the copies (or the wish) the Add row asked for when the job is done, with its own Undo, and says so on the Add page. Updating from 3.3 turns the default picture order into the new default and splits a changed one into the catalogue and the API. See Pictures, prices and where they come from.
  • Planning, wishlists and money run on the 4.0 store. Complete sets ranks the copies with a gap by what a repair gains per unit spent, from the cached BrickLink quotes and the repair settings; a pin and the settings are saved and undone as events. Its Export names every line by BrickLink number and colour; an item BrickLink has no number for is left out of the file and named in the message instead of stopping the export. The Wishlist screen, the named lists (create, move, copy, archive, restore, Undo) and the BrickLink XML and Rebrickable CSV exports work by item id; a wish that cannot be named in the chosen format is left out and listed in the export summary. A wish id is now a uuid. Part-out value, retail on the wishlist, wish progress, exchange rates (a rate or the ECB's, converted figures marked ≈) and manual prices (Undo voids the observation) work as before.
  • Orders and Identify run on the 4.0 store. An order document (BrickLink XML, the store's e-mail, the BrickLink API) is placed line by line on items through the BrickLink type, number and colour number, looking in your collection's links and the catalogue together; a key that names several items is never guessed: the line stays unmatched, offers its candidates under Could be, and you choose. Review, counting, allocation to a copy's gap or to loose stock, hold, reconcile, the short list and the CSV export work as before; every save is one event with Undo, and an undone import keeps its document and lines as provenance. A total comes with its currency, and a currency can stand without a total (the e-mail's EUR; M.12). A set line cannot be allocated to loose stock (add the set as a copy). What is this? and Part to Inventory recognise a photo through Brickognize and list a number that names several items apart instead of choosing one. Manage → Add takes a photo again: it offers the matches, adds nothing until you choose one, and keeps the photo only with Keep photo.
  • Tools & Admin runs on the 4.0 store: Settings (currencies, retail country, the source order, freshness rules; a save is one event with Undo), Catalogues & keys (sources with their budgets, write-only key cards, and a Catalogue card that says what is loaded and names the command when the catalogue is missing or not activated), Values, Jobs, Bulk refresh prices, Statistics, Database (the check keeps its result as maintenance:database_check; the export is the collection file), Instruction files (a PDF belongs to a set; a booklet shows the files of the set with its number), Identify history and API tokens. A new collection starts with the freshness rules of 0.5. The catalogue is built on the server with python -m brickwork.store4, not from the browser; the app's catalogue command is the same operation. brickwork migrate4 is python -m brickwork.store4 migrate; the brickwork wishlist commands take wish ids as text. The BrickLink catalogue XML loader and the colour load are gone with the catalogue builds.
  • Unresolved items (identity admin) runs on the 4.0 store: the list holds the local items that may be a catalogue item, the links and statuses to check and the items with no number, and each row offers its decisions (merge, confirm or reject a link, link a BrickLink number, keep as unmatched, move to another kind), each with Undo. A merge moves every reference of a local item onto the catalogue item in one step and unmerge puts all of it back exactly. See Resolve unresolved items and merge items.
  • Collection sync and Import from BrickTracker run on the 4.0 store (M.8j). A pull places each item by its kind (a set as copies through the part-list preselection, other kinds as loose stock) with one receipt and Undo; a send names an item by its Rebrickable or BrickLink number and lists an item with no number as not on the site; the link is carried by the migration and the first sync compares everything. The BrickTracker import is rewritten on Rebrickable numbers: copies through Add's path with BrickTracker's marks on the part lines, loose parts and figures as stock, lots, wishes and flags, one receipt, one Undo. brickwork migrate and the "Build a new database instead" form are removed (a 3.3 collection moves with brickwork migrate4). The demo is rebuilt on a 4.0 collection. Two guards join the suite: no code uses (item_type, item_no) as an identity, and every query on part, figure and loose-figure lines leaves retired rows out.
  • Tools & Admin looks after the catalogue lifecycle (M.10 C, #112): Catalogue (the current build, Re-download and Rebuild as background jobs with progress, what changed and the copies whose part list changed), BrickLink item lists (load from a folder, what the last load did), Mappings and coverage and the Migration report with downloads. Settings gets Prefer BrickLink's part list for new copies and a reorderable Picture source order. A catalogue swapped in but not yet reconciled is reconciled when the app (or brickwork worker) starts, as a job the drainer runs; BW_MIGRATION_REPORT names the report folder.
  • GET /api/v1/health also returns the app version (app), so monitors and update checks need one call.
  • Error responses never carry database or operating-system error text (#76).
  • Security: certifi 2026.10.19, outside the range of the emSign root CA advisory (#81).
  • An API write that queues a catalogue import (adding a set, part or wish, or moving a wish to owned) now starts the import worker; before, the import waited until something in the web app started it (#121).