chore: release @alauda/doom

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@alauda/doom@2.6.0

Minor Changes

• #347 c6fe198 Thanks @youyongsong! - Fix a family of API-reference rendering defects where the components ignored facts already present in the CRD / OpenAPI sources, plus add offline integrity tooling.

  Correctness — endpoints and schema now read the source instead of guessing:

  • <K8sAPI> derives namespaced from the CRD's spec.scope instead of always defaulting to true, so Cluster-scoped resources no longer render an unreachable /namespaces/{namespace}/ path. The namespaced prop still overrides.
  • Endpoint paths use the resource's real plural from spec.names.plural instead of guessing with pluralize(kind), fixing hyphenated (vpc-egress-gateways) and irregular (alaudaloadbalancer2) plurals. A new plural prop is an escape hatch for OpenAPI-sourced resources. (toLocaleLowerCase → toLowerCase.)
  • When a page does not pass apiVersion, a multi-version CRD now renders the version kubectl resolves to — the highest-priority served version (GA > beta > alpha, apimachinery ordering) — instead of spec.versions[0]. This never publishes a served: false version. Both the schema and the endpoint-path version now come from this single resolved version. Configurable via api.crdVersion: 'preferred' | 'storage' | 'first'.
  • <K8sAPI> no longer renders endpoint paths it cannot derive. When an OpenAPI schema carries no x-kubernetes-group-version-kind — aggregation-layer documents routinely omit it — and no CRD backs the name, the group, version and kind used to fall back to empty strings and concatenate into /api// and /api///{name}, shipping a broken path on a green build. The endpoints section is now omitted, with a console.error naming the props to declare; the schema still renders. apiVersion + apiKind (plus apiGroup outside the core group) make the page render endpoints again.
  • /status (and the new /scale) endpoints follow what the source declares, not whether the schema happens to contain a status property — fixing both fabricated /status endpoints and missing ones. A CRD declares the subresource in spec.versions[].subresources; an OpenAPI document declares it by routing it, so its paths decide, and a document that routes the resource without a /status route renders none. A document that does not route the resource at all says nothing either way, so the schema property stays the fallback there. The new hasStatus prop overrides both.
  • x-kubernetes-int-or-string fields (carried under anyOf) now render their type (integer|string) instead of an empty cell.

  Anchors and badges:

  • Array-item schema sections (.spec.foo[]) no longer collide with their parent (.spec.foo) on the same HTML id; schema headings use a page-level stateful slugger, so every property section is uniquely addressable (HTML id uniqueness / WCAG 4.1.1).
  • OpenAPI operations without a summary no longer produce id="undefined" / href="#undefined" or bare numeric anchors; the heading id is derived from the method (and summary when present).
  • The <OpenAPIPath> Request Body required badge reads requestBody.required (the boolean on the request body) instead of the body schema's list of required properties.

  New configuration and tooling:

  • api.references accepts an object form { href, routePath?: string | false }, separating the link href from the page-identity key used to decide inline expansion. Plain string values are unchanged. routePath: false explicitly means "always link, never expand".
  • translate.copyOnlyDirectories overrides which directories are copied instead of translated (default unchanged).
  • New doom api check command: an offline validation of the local CRD / OpenAPI sources — every file parses, CRDs have the right kind and a unique name, filenames follow the <group>_<plural>.yaml convention, and OpenAPI definitions do not conflict across files.
  • New no-unresolved-api-ref lint rule flags <K8sAPI> / <K8sCrd> / <OpenAPIRef> / <OpenAPIPath> / <K8sPermissionTable> references that cannot be resolved, before they ship as blank pages. It also flags a <K8sAPI> whose group, version and kind can be derived from neither the schema nor a CRD nor explicit props, so that failure surfaces at lint time instead of as a missing endpoints section.
  • Deterministic source ordering: schema files are sorted, and the filepath / openapiPath map key no longer depends on process.cwd(), so pinning a source is stable across working directories and <OpenAPIPath> uses a consistent first-match.

  Other:

  • <K8sPermissionTable> renders a visible "not found" row instead of silently dropping an unresolved function.
  • API component chrome (Property, Type, Description, Required, Specification, API Endpoints, HTTP method, Common Parameters, Request Body, Response, …) is now translated via useTranslation (en/zh/ru) instead of hardcoded English.
  • API reference pages surface their top-level properties in the page outline (previously a two-line TOC), while deeper nested properties stay excluded.

  Downstream impact: the scope / plural / version / status fixes change the rendered endpoints on already-published pages (measured: immutable-infra-docs 8, asm-docs 4, aml-docs 4, acp-docs 3, plus fabricated /status across ~19 pages). namespaced (docs/*/usage/api.md) and the CRD default-version behavior were documented public defaults; downstream docs should re-review their API pages after upgrading.

  The OpenAPI-branch /status change was measured against the full consumer corpus (222 <K8sAPI> / <K8sCrd> tags across 11 repositories; 26 resolve to OpenAPI schemas, all of them in acp-docs): no page changes, because every document that routes one of those resources also routes its /status. The two pages whose documents do not are covered by the fallback rather than losing endpoints.