docs: upgrade guide site to @nebari/starlight v0.2.0#21
Merged
Conversation
The shared theme's v0.2.0 raises its Astro peer floor to >=7.0.6, so the bump forces a framework upgrade. Move to the versions the theme was built against: Astro 5 -> 7 and @astrojs/starlight 0.33 -> 0.41. - Migrate the markdown config off the Astro-7-deprecated markdown.rehypePlugins field to unified() from @astrojs/markdown-remark (now declared as a direct dependency), preserving the rehype-base-links pass. Clears the build's only deprecation warning. - Update the branding test for v0.2.0's redesigned typography: headings are Space Grotesk (not Poppins) and the accent maps through --nbr-brand, a magenta-violet derived from --nbr-primary. Build is clean and all 11 build tests pass on both the production subpath and the PR-preview root base.
|
📄 Docs preview for |
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
1 participant
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.
What
Updates the guide site (
docs/site) to the shared@nebari/starlighttheme v0.2.0.The theme's own API is unchanged (same
nebari({ logoHref })plugin, no internal imports on our side), but v0.2.0 raises its Astro peer floor to>=7.0.6. That turns the bump into a framework upgrade, so this moves to the exact versions the theme author built v0.2.0 against:@nebari/starlight^0.1.6^0.2.0astro^5.0.0^7.0.6@astrojs/starlight^0.33.0^0.41.3@astrojs/markdown-remark^7.2.1(now direct)Changes
astro.config.mjs: Astro 7 deprecated the top-levelmarkdown.rehypePluginsfield. Migrated therehype-base-linkspass to the officialunified({ rehypePlugins: [...] })processor from@astrojs/markdown-remark(GFM and SmartyPants stay on by default). This clears the build's only deprecation warning.test/build.test.ts: v0.2.0 redesigned the theme's typography. Headings are now Space Grotesk rather than Poppins, and the accent maps through--nbr-brand(a magenta-violet derived from--nbr-primary) instead of--nbr-primarydirectly. Updated the Journey 4 branding assertions to match the theme's actual output; the test's intent is unchanged.package.json/bun.lock: version bumps above.Verification
bun run build: clean, no deprecation warnings, 8 pages.bun test: 11/11 pass (355 assertions).bun install --frozen-lockfile: clean, so the docs CI's frozen install stays green./building-a-software-pack/) and the PR-preview root base (BASE_PATH=/), and root-base links resolve correctly through the newunified()wiring.Local Node is 22.22 (Astro 7 requires >=22.12) and the docs workflow runs on Bun
latest, so there is no runtime pin to bump. The Cloudflare Pages preview deploy from this PR is the last check.