Yesterday I rejected grafana 13.x on a number I had misread. Seventy against a
hundred and sixty-two high findings is not a comparison when the two images do
not contain the same things: 12.4.9 bundles no plugins at all, 13.2.0 bundles
thirteen, and every one of those findings sits in a plugin binary. The 13.2.0
core is clean where 12.4.9 carries the one critical still on our books.
Size M, so no design document — the schema reserves those for L, and raising the
class to reach a nicer template is the same trick as redefining a criterion to
pass it. Gate one lives in the ledger instead.
The only real danger here is grafana's database migration, which has no way back.
That is why a verified backup is an acceptance criterion rather than a step.
Thore Cimbal
370a678d4f