Reference
Changelog
Release notes across every Fancy UI package.
Fancy spans two families of package — UI packages and Service & Tool packages — each its own independent repo with its own release cadence. The index below is generated from the package registry, so it's always current. Click through for the canonical release notes on GitHub; install commands and live demos live on the Packages page.
UI packages
| Package | Language | Release notes |
|---|---|---|
react-fancy |
TypeScript | Releases |
fancy-whiteboard |
TypeScript | Releases |
fancy-artboard |
TypeScript | Releases |
fancy-flow |
TypeScript | Releases |
fancy-sheets |
TypeScript | Releases |
fancy-slides |
TypeScript | Releases |
fancy-code |
TypeScript | Releases |
catalog-fms |
TypeScript | — |
fancy-term |
TypeScript | Releases |
fancy-tui |
TypeScript | Releases |
fancy-diff |
TypeScript | Releases |
fancy-echarts |
TypeScript | Releases |
fancy-mlm-ui |
TypeScript | Releases |
fancy-git-ui |
TypeScript | Releases |
fancy-x-files-ui |
TypeScript | Releases |
fancy-screens |
TypeScript | Releases |
fancy-3d |
TypeScript | Releases |
fancy-3d-babylon |
TypeScript | Releases |
fancy-3d-three |
TypeScript | Releases |
fancy-map |
TypeScript | Releases |
fancy-pwa |
TypeScript | Releases |
fancy-cms-ui |
TypeScript | Releases |
Service & Tool packages
| Package | Language | Release notes |
|---|---|---|
fancy-pixel |
TypeScript | Releases |
agent-integrations |
TypeScript | Releases |
fancy-inertia |
TypeScript | Releases |
holy-sheet |
PHP | Releases |
dark-slide |
PHP | Releases |
last-word |
PHP | Releases |
last-word-js |
TypeScript | Releases |
laravel-catalog |
PHP | Releases |
laravel-fms |
PHP | Releases |
laravel-fun-lab |
PHP | Releases |
fancy-mlm |
PHP | Releases |
fancy-mlm-js |
TypeScript | Releases |
fancy-git |
PHP | Releases |
fancy-git-js |
TypeScript | Releases |
fancy-git-github-php |
PHP | Releases |
fancy-git-github-js |
TypeScript | Releases |
fancy-git-gitlab-php |
PHP | Releases |
fancy-git-gitlab-js |
TypeScript | Releases |
fancy-git-bitbucket-php |
PHP | Releases |
fancy-git-bitbucket-js |
TypeScript | Releases |
fancy-flow-php |
PHP | Releases |
fancy-cf-relay |
TypeScript | Releases |
fancy-doc-commons |
TypeScript | Releases |
fancy-heuristics |
PHP | Releases |
fancy-cms |
PHP | Releases |
fancy-seo |
PHP | Releases |
fancy-x-files |
PHP | Releases |
fancy-x-files-js |
TypeScript | Releases |
fancy-auto-common |
TypeScript | Releases |
fancy-brand-icons |
TypeScript | Releases |
mcp-relay-client |
Polyglot (bash / Python / TS / Go) | Releases |
fancy-query |
TypeScript | Releases |
dark-slide-js |
TypeScript | Releases |
holy-sheet-js |
TypeScript | Releases |
fancy-app-update |
TypeScript | Releases |
fancy-term-host |
TypeScript | Releases |
fancy-file-commons |
TypeScript | Releases |
fancy-heuristics-js |
TypeScript | Releases |
fancy-features-js |
TypeScript | Releases |
fancy-catalog-js |
TypeScript | Releases |
docs-mcp |
TypeScript | Releases |
fancy-cli |
TypeScript | Releases |
Versioning
Every package follows semver. Minor versions add features; patch versions fix bugs; majors are reserved for breaking changes (we ship those rarely and document them with codemod hints where possible).
How releases work
npm packages (React/TS) publish via GitHub Actions Trusted Publishing (OIDC) — no tokens, signed provenance, deterministic supply chain. Each repo is independent; tag a release on main and CI does the rest:
cd fancy-term # or any package repo
# bump version in package.json
git commit -am "chore: release vX.Y.Z"
git tag vX.Y.Z
git push origin main --tags
# CI builds, signs provenance, and publishes to npm within ~60s
PHP packages publish via Packagist auto-sync from GitHub tags — bump composer.json (or rely on the git tag), commit, tag, push, and Packagist picks it up.
CLI + registry release notes
The fancy-cli CLI and the registry contract have their own release notes:
- fancy-cli releases — the vendoring CLI
- pa-ux-sandbox releases — registry + this docs site
If a major change affects the registry schema, we'll roll a $schema version (/schema/registry-v2.json) and run both side-by-side for a deprecation window. Consumers pinned to the old schema URL keep working.
