← Components

Vendored front-end

Dependencies and runtimes · vendored files. On a deployment this row is a control; the demo shows the row with the reading its source supports.

Evidence

Running

d3 v7.9.0, ECharts 5.6.0, 6 font families in 38 files

Built

40 files, hashed; fonts under SIL Open Font License 1.1

Latest known

d3 v7.9.0 (banner), ECharts 5.6.0 (version string), fonts as vendored

Source

core/web/static/fonts/README.md

Checked

2 hours ago

Cadence

none — record only

Mode

record only

State

current

Backup unit

The previous release.

Recovery

The previous release.

The five steps

Plan, back up, apply, verify, recover — in record only mode. On a deployment each step runs, is verified and lands on the audit trail; every component on the demo is current, so every step reads done.

1. ✓ done Plan Each vendored file's recorded version and hash are compared with the upstream the manifest checked; the plan names the files a release would replace.
2. ✓ done Back up The previous release stays kept; vendored files change only inside a release.
3. ✓ done Apply Replace the files on the workstation, record version and hash per file, build and sign the release.
4. ✓ done Verify Every served file hashes to what the release records, and the pages that load them render.
5. ✓ done Recover The previous release; its files come back with it.

Every row behind this reading (40)

History

Applies and recoveries of this row, from the update journal. On a deployment every apply and every recovery lands here as it completes.

No apply or recovery recorded for this row. The demo's journal holds one completed update, of Running image.

Acknowledge: keep as is until <date> because <reason> — on a deployment this line is a form, audited as system.component_acknowledged; the demo shows the words.

← Back to Components