Repository navigation
Brick Work 1.0.0
The first release after milestone B: its maintainer's real collection was set up from scratch through Get started on a test install, and every workflow ran on it. The schema stays 4.2, so a 0.9.0 collection needs no upgrade step, and going back to 0.9.0 means starting it on the same file. It is the first release whose compose.yaml pulls the published image, ghcr.io/ulef1005/brick-work:1.0.0 (amd64 and arm64, with build provenance and an SBOM): install and upgrade with docker compose pull; 0.9.0 and older still build with docker compose build (Upgrade Brick Work). Back up brickwork.db and secret.key before you upgrade, as always.
- The README describes 1.0.0 and introduces the crew. A new section, The crew, above Where we stand, gives each named Workbench workflow a paragraph: Part Spotter, Set Inspector, Part Runner and Matchmaker, with links to their guides; it replaces the short list of three. Where we stand describes release 1.0.0 (milestone B passed, the first release that pulls the published image), and the shipped list names Part Spotter, Storage and the tutorials.
- The upgrade guide shows how to check the published image (#190). Upgrade Brick Work now gives the two
gh attestation verifycommands for a pull-first release: one for the build provenance, one for the SBOM attached to the image, and what a failure means. The README names the SBOM check too. - Tutorial: finish a half-built set (#247). Finish a half-built set is a second learning path in the docs, on the same invented collection as the demo: check a half-built copy in Set Inspector, put the missing parts on a wishlist, receive a parts order against them and watch the copy turn complete. It links Check a set's parts, Manage wishlists and Receive a parts order. Its pictures come from
scripts/site_shots.py(newtut-stems), light and dark; the docs site now shipsdocs/img/tutorials/. - Tutorial: your first set, start to finish (#246). The tutorials page had no tutorial. It now has one: install from the README, the Get started first run (catalogue, keys optional), add one set, check its parts and see what is missing and where it shows up. See Your first set, start to finish.
- Tutorial: build from your bulk (#248). Build from your bulk is a learning path on the user docs site: set up storage with drawers, collect the missing parts of several sets in one pass with Part Runner, then let Matchmaker show the sets your loose stock finishes. Phone and desktop pictures, light and dark, come from
scripts/site_shots.py(new stemsbulk-*). - Tutorial: script your collection (#249). Script your collection is a learning path on the user docs site: create an API token, read and change the collection with the API and the command line, then connect an assistant over MCP and ask it about the collection. Every command and output was run on the invented showcase collection.
- The SBOM attestation uses
actions/attest(#190). The release workflow's SBOM attestation ranactions/attest-sbom, which GitHub has deprecated; it now runsactions/attestv4.2.2 (pinned by SHA) with the same subject, SBOM and registry push. - No empty band under the phone's bottom navigation in the browser (#245). The bottom bar always reserved at least 34 px below its icons, so in Safari, where the browser's own toolbar already sits at the bottom, an empty strip showed under it. The bar now reserves only the space the phone reports: nothing in the browser, the home-indicator space in the installed app. Page content, sheets and save bars still sit just above the bar. The approved phone (390 px) screenshots change by that strip.
- The demo's picture note fits its tile (#197). On the demo, a tile with no picture said where the app gets pictures (Loads from BrickLink when you add the set), even in a list row's small thumbnail, where the sentence spilled out of the tile. The note now goes only into a picture box (
.bc-picture,.bw-picture,.check-picture,.scan-tile) at least 120 px wide; any other tile keeps the app's short No image. The demo page check fails if a note leaves its tile. - The copy of the upstream changelog is gone (#237).
docs/upstream-CHANGELOG.md, the upstream project's release history kept from the fork, is removed; this changelog links the upstream repository for releases 1.4.2 and older. The credit in the README and THIRD_PARTY_NOTICES stays. - The Add search field sits right under the ways to find (#221). On Manage › Add, step 1 put What and Where above the Search, Paste, File and Photo tabs and the search field, so on a phone the field you type into sat below the first screen. The field (or the file and photo choosers) now follows the tabs directly, then What and Where in one row (stacked on a phone), then the results and Review. Nothing else changed, and the Tab key follows the new order. See Bring your collection in from another app.
- The install and upgrade steps for 0.9.0 say
docker compose build(#238). The README and Upgrade Brick Work told you to check outv0.9.0and rundocker compose pull, but that tag'scompose.yamlbuilds the image from source and names no published one, so the pull fetched nothing useful. For 0.9.0 the steps now saydocker compose build, and going back to 0.9.0 or older does too. The pull-first install, and the provenance check of the published image, start with the first release cut after 0.9.0. The tag itself is unchanged. Back up and restore and the Pages landing page say the same. - The Pages landing page no longer lists Collection sync as planned (#239). Its roadmap row said sync was planned although the page's own section says it is available for Rebrickable and Brickset; the row now reads Collection sync with BrickLink, the part that is still planned. The page also said the catalogue uses your own keys; it now says what the README says: the catalogue comes from Rebrickable's public download and needs no key, and your keys add prices, pictures and sync.
- An order e-mail line for a Technic figure in an unknown colour is no longer placed without a colour (#239). A line such as "Red Technic Figure ..." for an old Technic figure that the catalogue holds as a part was placed as that part in no colour even when the e-mail's colour name was not known here, where an ordinary part says The colour name is not known. The figure now takes the no-colour path only when the line names no colour; a named colour that is not known leaves the line for you to match, with that message.
- Lists say the right noun before the page's script runs (#239). The Instructions list's subtitle and Show button said "instructions" until the script replaced it with "booklets", and the Wishlist said "1 wishlist" or "3 wishlist". Both now read "booklets", "1 wish" and "2 wishes" from the first paint, with the same nouns the script uses for every list.
- The Wishlist chips have their gap, and Undo shows once (#224). On Planning › Wishlist the list chips (All lists, Wishlist and your own lists) touched each other; they now have the 8 px gap of the other chip rows. After a save the line read Saved · Undo with an Undo button under it, so Undo showed twice. It now reads Saved with the Undo button beside it on one line, as in Set Inspector. See Manage wishlists.
- Get started and Statistics sit at the top of Tools & Admin (#219). Manage › Tools & Admin now opens with two cards on the soft accent tint, Get started (with how many steps are done) and Statistics, side by side; on a phone they stack. The whole card is a link. The other groups follow in their usual order. See Settings and maintenance.
- Statistics charts read at a glance (#220). Tools & Admin › Statistics drops the cards: two charts sit side by side on a wide screen and one under the other on a phone, each row one line (label, bar, value). All four charts share one scale, so a bar means the same number of copies everywhere, with one note under them instead of one per chart. Each title states its point from your data ("Only 5 copies are complete", "Harbour is the biggest theme, 3 copies"), the headline reads "9 of 25 copies are incomplete", and completeness is in status order (Complete, Incomplete, Not checked, Sealed). After six rows a long tail folds into one outlined row such as "14 more themes". See Settings and maintenance. The approved Statistics screenshots change with it.
- Jump search is calmer (#216). In the search that opens from the top bar (Jump to a set, copy, figure or part, also ⌘K), the highlighted result row is now a soft neutral grey-beige with normal text instead of a clay-tinted fill, and the search field has a thin clay outline instead of a heavy one. The colours follow the light and dark modes; nothing else about the search changed.
- Found 1 on the set page, a missing-only check and a three-step end of a check (#215, #222, #214). Every missing part card on a copy's page has Found 1, which lowers its missing count by one with Undo and leaves the loose stock alone; where the card has Take N, it is a text link under it. Check missing only, beside Check parts, starts a Set Inspector run over just the parts the last check left missing (Missing part n of N, each showing what was missing since the last check); the API's
starttakesscope: missing. The end of any check now shows three steps, 1 Skipped, 2 Missing, 3 Save: you can check the skipped parts at once (recheckin the API) or leave them unchecked, then work through Missing so far. The progress bar in a check now spans the full width. See Check a set's parts. - Found 1 no longer moves a part to the top of Missing so far (#213). In Set Inspector, selecting Found 1 on a part that was still missing afterwards, or answering a listed part again, moved it to the top of the Missing so far list, so the list reordered under your finger. A part already listed now keeps its place, and only a new gap goes on top. See Check a set's parts.
- Items in a storage link to their pages (#223). On Workbench › Storage, the sets, minifigures, parts and other items in a storage were listed as plain text. Their names now open the item's page: a set opens on that copy, anything else on that loose stock. A lot's name stays text, since a lot has no page. In select mode a click on a name still selects the row. See Storage.
- Sort sets by date added (#226). Collection › Sets has a new sort, Date added: when a set came into Brick Work, its newest copy for a set with several. Picking it turns the order to newest first; Ascending turns it round. A collection brought in by an import or a migration has one date for all of it, so those sets keep number order among themselves; sets added from then on sort by when you added them. The API's
GET /copiestakessort=addedtoo. - The Add review shows the set's picture (#217, second half). Reviewing a set, minifigure or other item Brick Work had no picture of showed No image until after Add. The review now fetches and stores the picture when the row is shown (the same sources, order and budgets as the pictures step; a source without one is passed over), and the tile fills in place. The page's line now reads Nothing is saved before the last step, except the pictures fetched to show you. A part waits for its colour. See Pictures and prices.
- A new set's parts get their pictures (#217, first half). Adding a set queued the picture of the set only; its parts and minifigures showed No image until Refresh pictures. Add, and a Fetch from Rebrickable follow-up, now queue the pictures the new copies' parts and figures still lack, as one bulk action that runs after your own work. See Pictures and prices.
- Jobs update live (#218). On Manage › Jobs, only a job's progress bar was polled, and its last update set the bar back to the finished steps and read Import queued for a running job. The state, the step counts and the Bulk actions rows changed only on a reload. While anything is queued, running or waiting, the page now fetches its job area again every five seconds and swaps it in, so states, counts, bars and new jobs show without a reload. When a fetch changes nothing the wait doubles, up to a minute, so a job waiting hours for its budget does not re-render the page every five seconds; a settled page looks once a minute. The search, filters and an open … failed · why list stay as they are, nothing is swapped while you are on a button in the job list, and a hidden tab does not poll. A running import on Add now reads Importing · pictures · 38 of 112 and its bar keeps the running step's share. See Settings and maintenance.
- Breaking for MCP clients: the wishlist tools have plain names (#152).
post_wishlistsiscreate_wishlist,patch_wishlists_idisedit_wishlist,delete_wishlists_idisarchive_wishlist,post_wishlists_id_restoreisrestore_wishlistandpost_wishlists_id_transferistransfer_wishes, with descriptions that say what they do. An assistant or script that calls an old name gets unknown tool and must use the new one; the arguments are unchanged. The REST API and every other tool are unchanged. This is the one rename before v1.0.0 (ADR 0017, amendment of 8 Nov; MCP). - The Workbench workflows have new names (#204). Part to Inventory is Part Spotter, Check Set Parts is Set Inspector, Part Picker is Part Runner and Matcher is Matchmaker, in the navigation, page titles, docs, the README and the site. The old names still work in the jump search, and the addresses, API operation ids, MCP tool names and CLI commands are unchanged.
- The demo and every picture on the README and the Pages site are the built app, on an invented collection only. The demo (
/demo/) shows 22 invented sets (25 copies) over 1989-2023 and a dozen themes with part lists and 44 figures, 8 incomplete copies with missing and damaged parts and 3 missing figures, 90 kinds of loose parts and 33 loose figures in nested storage, gear, books and catalogs, four wishlists with maximum prices, three orders and prices, and it shows Gear, Books, Catalogs, the Matcher, Orders and the Manage pages. None of the design test data's real-named sets, figures, wishes or licensed parts appears: a catalogue item whose name matches the licence list inbrickwork/demo/showcase.py, or a part that is a printed design, is left out. It lives in its own layer, so the screen gate's world and approved baselines are unchanged, and it is built with a fixed clock. Every item has an original black-and-white line drawing instead of an empty picture tile (design/demo-art/, drawn byscripts/demo_art.py, stored as ordinary pictures with the source Demo illustration). The screenshots (README, landing page, use cases, workflows) replace the design project's mock-ups with captures of the running app on that world (scripts/site_shots.py); the sync picture is the built Collection sync screen and is no longer labelled a preview. - Brickset metadata asks for many sets in one call (#194). The Fetching set metadata step asked Brickset about one set per
getSetscall, and Brickset allows 100 of those a day, so a collection of N sets took N/100 days to import. The step now also takes the other queued or waiting jobs whose next step is Brickset metadata, up to 500 sets in all, asks for them in one call and finishes each job's step with its own result (a set Brickset does not return is not found, as before). The call counts once against the daily budget of 100, which is unchanged. If the call fails, the other jobs stay as they were. - The README describes 0.9.0. Where we stand says 0.9.0 is the first stability release and v1.0.0 follows milestone B; the intro and Catalogue, keys and jobs say the catalogue is built from Rebrickable's public download (no key) with BrickLink item lists optional, instead of BrickLink's catalogue XML; the Shipped list names Get started, the other kinds, e-mail and XML orders and the item lists; the services table shows collection sync as available for Rebrickable and Brickset. The Pages landing page, the use-cases page and the tutorials index say the same (no more Pre-1.0,
brickwork migrateordocker compose buildas the install step), and the settings reference no longer namesbricklink-catalog.db. Settings and maintenance has the details. - Install from the published image (#78).
compose.yamlnow namesghcr.io/ulef1005/brick-workat the release's version and keepsbuild: .as the fallback, and the README install is pull-first: clone the release tag, makedata/writable for uid 1000, thendocker compose pull. Upgrade is checking out the new tag anddocker compose pull; going back to 0.8.x or older, which have no published image, still needsdocker compose build. Upgrade Brick Work and Back up and restore say the same. A test keeps the image tag equal to the app version. - A BrickLink figure that the catalogue knows as a part is that part (#150). BrickLink files the old Technic figures (
tech028,tech039) as minifigures, while the catalogue links the same numbers to Rebrickable parts. A BrickLink order line, a BrickLink subsets list orGET /lookup?provider=bricklink&kind=minifigurethat names such a number found no minifigure and made an unidentified one. When no minifigure holds the number and exactly one part holds the very same BrickLink number, it now resolves to that part, as a part line in no colour. A catalogue minifigure still wins, several parts keep today's behaviour, and no other number is tried. Figures already made unidentified keep resolving to themselves. - The Wishlist on a phone has no empty gap under the list chips (#141). At phone width, Planning › Wishlist left about half a screen of empty space between the list chips and the Manage lists, Export, Print and Download CSV buttons. The buttons and the search now follow the chips directly, as on a wider screen. Two approved phone screenshots (light and dark) change with it.
- Counts of one use the singular (#180). The Sets page said "1 copies", the Catalogs page "1 catalogs", and the filter panel's button "Show 1 parts" and the like. A list's subtitle and its Show button, and the Wishlist count, now use the singular for exactly one and the plural otherwise, for every kind.