Release Safety
Current package state
The six public Combric packages are available on the npm registry at the
synchronized 1.1.1 version documented by this snapshot: @combric/tokens,
@combric/layout, @combric/react, @combric/tailwind, @combric/cli, and
@combric/guard. All six are currently published on npm. The COMBRIC-WEB
release-quality check installs these packages from https://registry.npmjs.org/
in a temporary consumer project and verifies their public entry points. Registry access is required; the check does not
substitute workspace packages, source paths, or local tarballs.
The first-publication bootstrap instructions describe a one-time registry
constraint, not current publication status or authorization. These package
names already have public 1.1.1 releases. Do not repeat bootstrap or attempt
to republish 1.1.1. The consumer check is evidence of availability and
compatibility only; it cannot grant publication authority.
Separate release decisions
- A framework release changes the synchronized package version and follows the framework repository’s approved release process. Semantic Versioning applies to the documented package APIs, types, CSS entry points, CLI, and Guard contracts. Breaking changes require a major version; compatible features use a minor version; compatible fixes use a patch version.
- A COMBRIC-WEB release updates the site, documentation snapshot, consumer checks, and static output. It does not publish framework packages.
- Publishing packages requires separate explicit Product Owner authorization and the framework repository’s protected release workflow. A green website check or merged documentation change is not publication approval.
- Hosting and domain selection are separate again. This repository has no configured production host or domain, and this milestone does not deploy.
The static build and release-quality check run without
COMBRIC_DOCS_SITE_URL. Set that variable only after the production origin has
been deliberately selected and approved.
MANUAL GATE — production hosting/domain not yet selected/configured
Release-quality check
From a clean checkout, install the web application’s locked dependencies with
pnpm install --frozen-lockfile, then run pnpm release:check. The gate covers
formatting, lint, types, docs and package-boundary invariants, public-registry
consumer smoke tests, a static build, versioned/latest/legacy routes, Pagefind
output, and Playwright/axe accessibility regressions on desktop and mobile
Chromium. It is a bounded regression suite, not a WCAG certification or a
claim that every consumer application is accessible.
The checked-in CI runs the same release-quality command. A successful run does not publish packages, configure hosting, or deploy the website.