Repository navigation
Release 0.9.0 - #14
Merged
Merged
Conversation
cudoc-eleventy splits front matter by the rules gray-matter follows under Eleventy's default options, so collection still renders the text Eleventy renders, and reads the data as YAML 1.2 with the parser the other hosts use, or as JSON for `---json`. That drops gray-matter's js-yaml 3 and its advisories from every Eleventy site. JavaScript front matter would have to run to be read, so it fails collection naming the file, as does front matter that is not a mapping. A MarkdownItHost's frontmatter hook now receives the collected document's id and filePath, which those errors name. The adapter reference and the Eleventy guide describe the split, the languages read and the options a site should leave at their defaults.
An exported site's home document now lists its contents on the right like every other page. A page with no heading to list leaves that column out instead of drawing it empty, and a generated landing page, which lists the navigation in its body, takes the whole width. The language menu is a <details class="menu"> whose summary shows the page's language and opens the others, and the theme menu is the same drop-down with a Light and a Dark button instead of the browser's own select. Both are drawn in the site's colours. While one is open, the summary's ::before covers the viewport under the list, so a press elsewhere closes it without a script, and the header rises above the review runtime's controls. With themeSwitch, the script also closes the open menu on Escape or when focus leaves it, and marks the theme data-theme holds, so a choice the browser refuses to store still shows.
npm audit found advisories published after 0.8.0 in the root and the examples. The root and the Docusaurus example and guide pin postcss-selector-parser 7.1.6 and tinypool 2.2.0 beside their other overrides, and the root moves to vitest 4. The examples are tested on Next.js 16.4.2, Nextra 4.6.0 on Next.js 15.5.28 and Eleventy 3.1.7, whose dependencies carry none of the advisories Eleventy 3.1.6 had, so its row leaves the advisory table. Next.js is supported from 16.4, the release the example now tests. Nextra stays on 4.6.0: 4.6.1 takes zod ^4.1.12, and from zod 4.4 nextra-theme-docs rejects its own layout props without children, so no page prerenders. The supported-versions section says why. Three cudoc-export tests that build a site or run the CLI get a 60 second timeout, since a slow CI runner took them past the 5 second default. Every package moves to 0.9.0 with its siblings pinned to it, the root and example lockfiles follow, and the export samples are rebuilt with the new generator version. The release notes list what to act on when upgrading.
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.
Bumps every package to 0.9.0 and pins the sibling dependencies to it. The release notes are in
docs/release-notes.mdanddocs/release-notes.ko.md, under## 0.9.0, including what to act on when upgrading.cudoc-eleventyno longer depends ongray-matter. It splits front matter by the rules gray-matter follows under Eleventy's default options and reads the data as YAML 1.2 with the parser the other hosts use, or as JSON for---json;---jsand front matter that is not a mapping fail collection, naming the file. AMarkdownItHost'sfrontmatterhook receives the document'sidandfilePath.<details>drop-downs drawn in the site's colours. A press elsewhere closes them without a script; withthemeSwitch, Escape and a focus move do too.npm auditreported after 0.8.0 are cleared or tabled: the root and the Docusaurus example and guide pinpostcss-selector-parser7.1.6 andtinypool2.2.0, the root moves to vitest 4, and the examples are tested on Next.js 16.4.2, Nextra 4.6.0 on Next.js 15.5.28 and Eleventy 3.1.7. Next.js is supported from 16.4. Nextra stays on 4.6.0 because 4.6.1, with the zod its range installs today, fails every prerender on a layout props check; the supported-versions section says so.cudoc-exporttests that build a site or run the CLI get a 60 second timeout after a slow runner took them past the 5 second default.Verified on the release machine:
npm ci,npm run build(andbuild:webpackinnext-mdx) andnpm auditin each of the six examples (Next.js, Eleventy and export report nothing; the Docusaurus, Nextra and VitePress findings are the ones tabled inexamples/README.md),npm run typecheck,npm run format:check,CUDOC_STRICT=1 npm test(70 files, 1872 tests) andnpm run test:scripts(all five, including the guide check and the export sample comparison). An independent review of the whole diff found no blocking defect; its four wording corrections are applied.Every package is already on npm with a trusted publisher for this repository and
publish.yml, so the whole release goes out from the workflow.