CODESHOPQC
← Back to CodeShop QC
Last updated 17 August 2026
This page exists for one reason: so you can see whether the product is still being worked on before you put a job’s records in it. Dated, newest first, and only things you would actually notice.
No version numbers, and the releases are dated instead. Changes ship when they are ready rather than in numbered releases, so a release is identified by the day it went out. A number would imply a history that can be checked against something; a date is just the day.
This page starts where the record starts. CodeShop QC was built before it had a changelog, so what is below is not the whole history of the product — it is everything since there has been a file that has to agree with what shipped. Nothing has been backfilled from memory.
17 August 2026
A Manufacturer's Data Book compiled out of CodeShop QC now carries the version of the software that assembled it, printed small on the cover beside the document number and the compiled date. That is the answer to the question asked when a book is challenged later: which build produced this, and can it be reproduced.
The same version is published at /version.json, so what is deployed can be checked from outside the app rather than taken on trust.
Dated entries, newest first, generated from a changelog in the repository rather than edited by hand. The point of generating it is that the page, the version printed on your data books, and the version the deployed site reports cannot disagree with each other - a test fails if they ever do.
Nothing before today has been written up. CodeShop QC was built before it had a changelog, and reconstructing a release history from memory would be inventing one.
Only user-visible change is listed — something you could notice using the product, or a resource we published. Off the list: infrastructure, documentation, test work, mail and DNS setup, and internal refactoring that changed no behaviour. There has been a lot of all of it.
Saying so matters, because a changelog that filters silently reads as a complete history when it is not. If you want to know whether something specific shipped or is planned, ask.
Release notes — codeshopqc.com/release-notes