Skip to content

v3.0.0 — Rename and identifier reset

Choose a tag to compare

View all tags
@ikelaiah ikelaiah released this 05 Oct 01:54
· 12 commits to main since this release
v3.0.0
cf0dd31

SQL Cartographer v3.0.0 — Rename and identifier reset

The project was named ProcFlow until v2.7.0. From v3.0.0 it is
SQL Cartographer, published at
ikelaiah/sql-cartographer.
This is a breaking release: the rename reaches user-data-facing identifiers,
so saved work from v2.7.0 and earlier does not load. There is no migration
path.

Highlights

  • New name everywhere that matters. The GitHub repository, the npm package
    (sql-cartographer), the product name in prose, the release archive, the
    logo, and the CI and packaging scripts all follow the new name. The old
    ikelaiah/ProcFlow repository URL redirects automatically.
  • One consistent wordmark. The logo now reads sql>cartographer, the
    exported Mermaid provenance header reads %% sql-cartographer provenance,
    and generated SQL headers are prefixed sql-cartographer.
  • Failure output that names the failure. npm test previously printed only
    erd-ui: 66/68 tests passed, which is enough to know something broke and
    not enough to know what. Each failing case is now printed with its name and
    detail.
  • Hardened ERD interaction polls. The erd-ui polls that wait for
    requestAnimationFrame-driven overlay drawing allow 10s instead of 3s, so a
    contended CI runner does not drop cases a desktop browser passes.

Breaking: user-data identifiers

Anything saved before this release is stored under the old identifiers and
will not load. Export what you want to keep before upgrading.

Kind v2.7.0 and earlier v3.0.0
Browser storage keys procflow.workspace, procflow.erd.layout, procflow.erd.query sql-cartographer.workspace, sql-cartographer.erd.layout, sql-cartographer.erd.query
Saved-query file format procflow-erd-query sql-cartographer-erd-query
ERD-layout file format procflow-erd-layout sql-cartographer-erd-layout
draw.io XML attributes data-procflow, data-procflow-kind data-sql-cartographer, data-sql-cartographer-kind
draw.io diagram id procflow-page sql-cartographer-page
Default download names procflow-report, procflow-estate, procflow-workspace.json, procflow-query-<fp> sql-cartographer-report, sql-cartographer-estate, sql-cartographer-workspace.json, sql-cartographer-query-<fp>
Release archive procflow-vX.Y.Z.zip sql-cartographer-vX.Y.Z.zip

Before upgrading:

  1. Saved queries — use Query → Export to write a procflow-query-*.json
    file. After upgrading, Query → Import accepts the same file: the importer
    recognises a procflow-erd-query payload and re-saves it under the new
    format, so only the file needs to survive the upgrade.
  2. ERD layouts — use Export to write a procflow-erd-layout-*.json file.
    Layout files are read by format tag rather than by filename, so an old
    export imports cleanly and is rewritten under the new tag.
  3. Workspaces — a procflow-workspace.json export is not readable by
    v3.0.0. The workspace format is version-checked and rejected rather than
    half-imported. Rebuild the workspace after upgrading, or stay on v2.7.0
    until you no longer need it.

Browser storage is not migrated. The old procflow.* keys remain in the
browser but are never read; clear them manually if you want the space back.

Accuracy and limits

  • No analysis, export, or query-builder semantics changed. The rename is a
    mechanical identifier substitution: every golden, fuzz, adversarial, and
    security fixture passes with the same expectations as v2.7.0, and the
    fixture-corpus metric numbers are identical.
  • The docs/metrics-v*.json snapshots for v2.7.0 and earlier keep the
    generator label that release produced, except metrics-v2.7.0.json which
    was regenerated with the new label so the correctness workflow's snapshot
    currency check stays meaningful. The metric numbers are unchanged either way.
  • Historical documents keep the old name on purpose: docs/archive/, the
    canonical release notes for v1.14.0 through v2.6.0, and the CHANGELOG.md
    entries for those releases describe what shipped under it.
  • Browser automation depends on a locally installed Chromium/Edge/Chrome;
    npm test honours CHROME_PATH and fails with a clear message otherwise.

Verification

The final local verification recorded for this release includes:

  • npm run lint (Biome) passing with 0 errors;
  • npm run typecheck and npm run build passing;
  • npm test (scripts/test-all.mjs) passing all five browser suites over a
    local static server: golden 221/221, fuzz 400 deterministic mutation cases,
    ui 32/32, erd-ui 68/68, security 6/6;
  • npm run test:file (local-file startup smoke) passing;
  • npm run metrics confirming the v3.0.0 fixture-corpus snapshot is current;
  • npm run benchmark completing the repeatable scalability run;
  • npm run package:smoke passing archive structure and local-file startup on
    sql-cartographer-v3.0.0.zip;
  • CI runs the same gate plus Firefox smoke and release-consistency checks.

Upgrade and distribution

Download sql-cartographer-v3.0.0.zip from the GitHub release or clone
ikelaiah/sql-cartographer.
The runtime footprint is unchanged apart from the identifier rename: the same
index.html, styles.css, and dist/ modules. Open index.html (or
erd.html) in a current Chromium, Firefox, or Edge browser.

If you are linking to the old repository, update the URL — the redirect works
for clones and releases, but GitHub Pages URLs do not redirect and the live
demo is now at https://ikelaiah.github.io/sql-cartographer/.

Assets 4
Loading