Support matrix
What this documentation build is pinned to. When you open a reference page, these numbers are the ones that apply.
| Artefact | Value |
|---|---|
| Federation wire contract | 2026-05-plexon-federation-v3 |
@chbrdk/plexon-federation | 0.2.1 |
@chbrdk/dic-app | 0.1.0 |
| Docs generator | Docusaurus 3.10.2 |
| OpenAPI download | federation-v3.yaml |
| SDL download | entities.graphql |
| Build manifest | dic-portal-manifest.json |
Channels
| Channel | Meaning |
|---|---|
latest | Last intentionally published docs + package combination |
next / preview | Staging docs host (this portal) — may lead packages slightly |
local | npm run portal:build on a laptop |
The manifest’s channel field records which lane produced the file.
How to upgrade safely
- Read the SDK changelog / release notes for
@chbrdk/plexon-federation. - Bump the package, regenerate OpenAPI (
federation:openapi) in the control-plane repo, run contract checks. - Rebuild this portal so YAML/SDL downloads match the code you ship.
- Re-run onboarding and revoke on staging.
Compatibility tips
- Product apps should depend on SDK semver, not on copying Zod files.
- UI chrome should depend on
dic-appsemver +@msqdx/ui. - Do not mix a new SDK with an old Control Plane that still speaks another contract header.