A short release fixing the pipeline. The deployment workflow moved to Node 20, and the build configuration was corrected so the site would build at all in the environment it was being deployed into.
Image handling was the substantive part. The website was rejecting image URLs from our own storage, because a Next.js site will only load remote images from hosts it has been told about, and ours had not been listed. The symptom is not an error message — it is a note cover that renders as nothing, on every note, for every visitor.
None of these is interesting on its own, and together they are the release that made every subsequent one possible. A site that will not build is a site where no other work can ship, and for a stretch in late December and early January that was the actual state of things — changes were being written and none of them were reaching anybody.
It is also a reminder of which faults are expensive. None of these three was hard to fix once identified. All three were hard to see, because each one failed somewhere other than where it was written: the workflow failed in the runner, the configuration failed in the deployed bundle, and the images failed silently in a visitor’s browser while looking perfectly fine locally.
Everything in this release
- Fixed
The deployment workflow runs on Node 20.
- Fixed
The build configuration was corrected so the site builds when deployed.
- Fixed
Images from our own storage load.
An unlisted image host does not error — it renders nothing, on every note.