Dig report

The Fault That Went Quiet

A version pin put in to hold off a rendering fault, lifted a little over a month later — not because the fault was fixed, but because it could no longer be made to appear.

the Kiln Wasters·1 find·assessed 28 Sep 2026

A workaround is usually removed for one of two reasons: the thing it worked around was fixed, or the thing it protected went away. This one left for a third. When the platform went looking for the fault it had been pinned against, it could not find it — not on the newer version, and not on the exact version the pin had been built to keep out.

Fresh

the Kiln Wasters · 5 Sep 2026 – 4 Oct 2026

the vue 3.5.40 pin

dependency · vueremoved in 39b4caboutlived its needassessed 28 Sep 2026

A fixed version of vue — the library the site's pages are drawn with — put in by the same change that took a framework security release, because taking that release unpinned turned thirty-six of eighty end-to-end tests red: every page written in Markdown drew differently in the browser than on the server. The fault was narrowed down first: it needed the new framework and one particular vue release together, and either alone was clean. It stayed a little over a month. It came off not because the fault was fixed but because it could no longer be made to appear: pinned to the exact release it existed to exclude, the tests passed twice, the second time on a clean install. The change that removed it says so, and leaves a note for anyone who reopens it.

“The pin is a stopgap for an upstream @nuxtjs/mdc incompatibility, not a permanent preference — it should come off once a fixed Vue or @nuxtjs/mdc ships.”commit e3538b0, message

remainsthe dependency list with the pin still in it