Skip to content

chore: retire legacy analytics formats — tracking #4913

Description

@NoopDog

Tracking issue for retiring the legacy analytics report formats (Jupyter Book/PDF and Google Sheets) across repos, keeping only the static analytics sites. Driving reason: the legacy toolchains dominate the analytics requirements and their recurring dependabot update PRs (see #4910 for details).

Order of work

Step 1 — parallel, either order (pure deletions):

Step 2 — only after both Step 1 items merge (they remove the consumers of the deleted code):

Step 3 — deletions can start any time; each repo's final requirements re-freeze happens after #4912 (they install the package from this repo's main, and matplotlib drops out in the same pass):

Every ticket ends with a fresh-venv generate_static_site.py verification run so the surviving static-site flow is proven intact at each step.

Follow-ups (non-blocking, spun out of review)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions