cloudflare/nimbus @cloudflare/nimbus-docs@0.19.1

on GitHub

Patch Changes

• #293 ff3ad76 Thanks @MohamedH1998! - Authored code samples render without openapi-sampler and @readme/httpsnippet: set samples.generate: [] to publish authored samples only, or one warning says what to install. Authored samples highlight in every language Shiki bundles. A spec with a schema property named $ref builds and publishes without reference warnings, and a $ref whose value is not a string is reported by its location.

• #293 85366b6 Thanks @MohamedH1998! - Cheaper API builds and a lighter Worker. The spec is parsed once for the walk and its ref-preserving copy, with a second parse only if the parser ever resolves in place. For an API with bundle: false, the "Prepared API pages" line says what changed when a version is rebuilt. Agent files are staged by clone and the search inventory reads the Markdown twins instead of rendering every page again. A server build reads the agent-endpoint manifest from _nimbus/agent-endpoint-assets/manifest.json instead of inlining it, and staging fails with a clear error if that file would exceed Cloudflare's 25 MiB static file limit.

• #293 a806887 Thanks @MohamedH1998! - nimbus-docs check no longer asks for rendering.collections when the api config is computed. It takes a zero-argument apiCollection() registration as an API collection, skips matching registrations against api entries, and says so in a "needs a build" note; the build enforces both.

• #135 1ee21b9 Thanks @dependabot! - Update the interactive prompts to @clack/prompts 1.8.

• #300 678d1e9 Thanks @MohamedH1998! - The dev server works with Astro 7.3.3: content edits refresh Markdown, llms.txt and discovery files again, and editing astro.config re-indexes collections before the restarted server serves.

• #293 796f348 Thanks @MohamedH1998! - Add routes.sections: "hierarchical" so an API collection's tag pages are served at the tag hierarchy's path (/api/zero-trust/devices/) instead of tags/<segment>/, and routes.tagSegments to set one tag's URL segment. Opt-in under resource-action-v2; coordinates and operation URLs do not change.