Sextant

Maintenance

Version support matrix

The reason to keep paying after the code is in your repo is that it stays correct as React and Next.js churn. This page is the contract behind that promise: the exact versions Sextant is supported on, and the versions it is tested against in continuous integration.

DependencySupported versionStatusTested in CI
Next.js16.2.6SupportedEvery push + scheduled canary
React19.2.4SupportedEvery push + scheduled canary
React DOM19.2.4SupportedEvery push
Node.js20.x (LTS)SupportedEvery push
Tailwind CSS4.xSupportedEvery push
Recharts3.8.xSupportedEvery push
TypeScript5.xSupportedEvery push (tsc --noEmit)

Supported versions are pinned in the package manifest and verified on every push. Listed versions are what we test and ship against; older majors are not guaranteed.

Maintenance posture

Sextant is open-core: you own the component source after one install. What a paid license buys is upkeep — a library that stays correct as the framework underneath it moves. Free chart libraries hand you a snapshot; we maintain ours against framework churn so the code you copied into your repo keeps working.

Every push runs the full suite — type-check (tsc --noEmit), unit tests, lint, and the registry leak-boundary checks — against the supported versions above on Node 20.

On top of that, a scheduled framework-churn canary job builds and tests Sextant against the Next.js / React canary and next releases. When an upstream change is going to break the widgets, we see it on our schedule — not in your production build. This is part of milestone M4 (Trust & procurement) on the public roadmap.

Procurement & provenance

For a maintenance and bus-factor review, two artifacts are public and kept current:

  • CHANGELOG — every notable change, in Keep a Changelog format, reverse-chronological.
  • ROADMAP — the maintenance plan and milestone status, including the framework-churn CI work in M4.

The current package version is 0.1.0. Version-support changes are recorded in the CHANGELOG and reflected here.