Graphora

Theme

Product demo

Releases ​

Graphora has no published package release. The current V0.1 notes are a draft, all package manifests remain at version 0.0.0, and the deployed site is a preview of repository builds. A successful site deployment does not publish npm packages or make the private source repository public.

Validate a candidate ​

From graph-library/ in an authorized checkout:

bash
pnpm install --frozen-lockfile
pnpm release:check

The release check builds packages, runs unit tests, type checks, lint and format checks, verifies generated API docs, builds all manifest examples, and runs the Playwright suite. Hosted CI mirrors this validation for pull requests, main, and manually selected candidates. It does not create tags, publish packages, or deploy the site.

Build the complete local site artifact separately:

bash
pnpm site:build

That produces dist/site with the landing page, rendered docs, API reference, examples, selected example source files, manifest, and revision marker. Site deployment has its own reviewed workflow and rollback procedure.

Publication blockers ​

Before any registry release, maintainers must:

  • choose a repository license and add matching package metadata;
  • confirm control of the @graphora npm scope;
  • choose author, repository, homepage, bug-reporting, and package metadata;
  • choose the first version and public, private, prerelease, or stable mode;
  • decide fixed or independent package versioning;
  • approve package access and provenance or trusted-publishing policy;
  • inspect package tarballs and approve the actual publish action;
  • document support and private security reporting routes.

The repository's package-publishing plan recommends a fixed package-family version for the first public release and Changesets before a repeated release cadence. Those are plans, not completed release infrastructure.

Compatibility expectations ​

There is no stable API compatibility promise for version 0.0.0. Pin work to a known repository revision, record that revision in bug reports, and read the current project status, API reference, and example source together.