Repository navigation
chore: bump package versions - #299
Merged
Merged
Conversation
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://changeset-release-main.nimbus-docs.com (commit f96b505)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
cloudflare-nimbus-bot
Bot
force-pushed
the
changeset-release/main
branch
6 times, most recently
from
October 26, 2026 09:56
63be977 to
d1e3040
Compare
cloudflare-nimbus-bot
Bot
force-pushed
the
changeset-release/main
branch
from
October 26, 2026 09:59
d1e3040 to
9ffb6f6
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
@cloudflare/create-nimbus-docs@0.8.1
Patch Changes
#135
1ee21b9Thanks @dependabot! - Update the interactive prompts to @clack/prompts 1.8.#290
9ae48e4Thanks @dependabot! - New projects start on Astro 7.3.3, which includes a security fix in its SVG optimizer.@cloudflare/nimbus-docs@0.19.1
Patch Changes
#293
ff3ad76Thanks @MohamedH1998! - Authored code samples render withoutopenapi-samplerand@readme/httpsnippet: setsamples.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$refbuilds and publishes without reference warnings, and a$refwhose value is not a string is reported by its location.#293
85366b6Thanks @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 withbundle: 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.jsoninstead of inlining it, and staging fails with a clear error if that file would exceed Cloudflare's 25 MiB static file limit.#293
a806887Thanks @MohamedH1998! -nimbus-docs checkno longer asks forrendering.collectionswhen theapiconfig is computed. It takes a zero-argumentapiCollection()registration as an API collection, skips matching registrations againstapientries, and says so in a "needs a build" note; the build enforces both.#135
1ee21b9Thanks @dependabot! - Update the interactive prompts to @clack/prompts 1.8.#300
678d1e9Thanks @MohamedH1998! - The dev server works with Astro 7.3.3: content edits refresh Markdown,llms.txtand discovery files again, and editingastro.configre-indexes collections before the restarted server serves.#293
796f348Thanks @MohamedH1998! - Addroutes.sections: "hierarchical"so an API collection's tag pages are served at the tag hierarchy's path (/api/zero-trust/devices/) instead oftags/<segment>/, androutes.tagSegmentsto set one tag's URL segment. Opt-in underresource-action-v2; coordinates and operation URLs do not change.