You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrades comark-content from 0.4.3 to 0.5.1, the version the upcoming Nuxt Content v4 module depends on. 0.5 removed the comark-content/sources/github source, so nuxt.com's GitHub-backed content instances (site, docs, cli, examples, module docs) now read GitHub through the generic forge source.
This branch started as an exploration of moving nuxt.com onto the Nuxt Content v4 module (nuxt/content-v4-temp#37). The module can't serve nuxt.com yet: every instance reads a repository at the commit its branch points to, and vercel.json skips deploys for content-only pushes, so even site can't ship with the build. That attempt is reverted in this branch, and its findings (six gaps in the module) are on nuxt/content-v4-temp#37. What's left here is only the dependency upgrade.
What changed
package.json: comark-content ^0.4.3 → ^0.5.1, and forges ^0.3.2 as a new direct dependency.
utils/factory.ts: github({ repo, branch, path, token, ttl }) becomes forge({ provider: github({ auth }), repo, ref, path }), with github from forges/github. The token is passed as forge auth when one is configured.
server/utils/content/instances.ts: the source option type comes from comark-content/sources/forge instead of sources/github.
pnpm-workspace.yaml: the comark override comment no longer names comark-content, which accepts comark 0.9 since 0.5.
No app, page, webhook, snapshot, search or l10n code changes.
Evidence
Check
Result
pnpm install --frozen-lockfile
✓ pnpm why comark → 1 version (0.9.0); pnpm why comark-content → 1 version (0.5.1)
pnpm lint, pnpm test:types
✓ exit 0
pnpm vitest run --project unit / --project nuxt
✓ 738 / 58 tests passed
pnpm build
✓ exit 0. The snapshot module resolved every ref and parsed from GitHub through forge: site snapshot 350a1a4: 1823 kB, plus examples, docs:4.x, cli:4.x and 6 module docs
✓ lint, typecheck, unit, bundle-size, CodeQL, Vercel
The built server (node .output/server/index.mjs, with a GitHub token) returned 200 for /docs/4.x/getting-started/introduction, /blog/v4, /raw/blog/v4.md, /deploy/vercel, /docs/4.x/api/commands/dev, /llms.txt, /api/navigation/4.x and /fr/docs/4.x/getting-started/introduction, and the blog post renders normally.
Worth checking before merging
The old github source cached each read for 24 hours (ttl); forge has no equivalent option. Reads go through withRef(sha), so they're for immutable commits, and parsed results still go through each instance's cache driver, but GitHub API usage under production traffic hasn't been watched on Vercel. Worth a look at the Vercel preview's logs, or after deploying.
The branch history contains the reverted v4 attempt; squash-merging keeps main's history to this one change.
ELI5
nuxt.com reads its docs and blog from GitHub through a library called comark-content. This updates that library to its newest version, which reads GitHub in a slightly different way. The site works the same.
Exploration: `@nuxt/content` v4 owns nuxt.com's own content (`site`),
defined in `server/content.ts` with `createNuxtContent()`. It serves it
under `/__nuxt_content`, snapshots it at build and generates its types;
the app reads it through the native `content` client and renders
documents with `<ContentRenderer>`. No v3 compatibility layer.
The docs, cli, examples and module docs instances stay on comark-content:
the module serves one surface under a fixed base path, so it can't hold an
instance per commit (`withRef`) nor several instances sharing a name.
- Bump comark-content to 0.5.1 (the module's), moving from the removed
`github` source to `forge` + `forges/github`
- `site` leaves the push webhook and `modules/snapshot`: it ships with
the deployment its push triggers
- Patch nuxt-agent-discovery to accept `@nuxt/content` v4
Amp-Thread-ID: https://ampcode.com/threads/T-01a1b537-979e-7255-b1d1-f4d6b0f37278
Co-authored-by: Amp <amp@ampcode.com>
A push that only touches `content/` skips the Vercel deploy (`ignoreCommand`), so `site` must keep
reading GitHub at the commit `main` points to and stay in the push webhook. The Nuxt Content v4 module
can't serve per-commit instances yet, so it no longer owns `site`.
Amp-Thread-ID: https://ampcode.com/threads/T-01a1b537-979e-7255-b1d1-f4d6b0f37278
Co-authored-by: Amp <amp@ampcode.com>
atinux
changed the title
feat: migrate to Nuxt Content v4 (native API)
chore: upgrade comark-content to 0.5 (Nuxt Content v4 exploration)
Nov 7, 2026
No actionable comments were generated in the recent review.
Walkthrough
The project upgrades comark-content and adds forges. The content source type and factory configuration change from the GitHub source to the forge source with a GitHub provider. The factory passes the configured branch as ref and sets token authentication only when ctx.token is present. Local-directory and override-path selection remain unchanged.
The dependency and source migration is mergeable on the available evidence; production GitHub API usage remains worth monitoring.
Pre-merge checks: 5
Check name
Status
Explanation
Title check
The title "chore: upgrade comark-content to v0.5.1" matches the main change. The PR upgrades comark-content from ^0.4.3 to ^0.5.1 in package.json, and the related source and factory changes follow fro…
Docstring Coverage
Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Description check
The description states the purpose of the change: upgrading comark-content from 0.4.3 to 0.5.1 and adding forges as a direct dependency. It names the affected files (package.json, utils/factory.ts, se…
Full details: Title check
Explanation
The title "chore: upgrade comark-content to v0.5.1" matches the main change. The PR upgrades comark-content from ^0.4.3 to ^0.5.1 in package.json, and the related source and factory changes follow from that upgrade. The title is short, specific, and names the primary change.
Full details: Docstring Coverage
Explanation
Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 1 functions across 2 files. (2 skipped: 2 unsupported.)
Full details: Description check
Explanation
The description states the purpose of the change: upgrading comark-content from 0.4.3 to 0.5.1 and adding forges as a direct dependency. It names the affected files (package.json, utils/factory.ts, server/utils/content/instances.ts, pnpm-workspace.yaml) and explains the move from the removed GitHub source to the forge source. It also lists verification steps and a reverted v4 attempt. The description is related to the changeset and is detailed, so the check passes.
Finishing Touches
Generate docstrings
Commit to this branch
Create a new PR
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: ab74aff3-3b2c-439c-aae7-952a0e72f86b
Commits
Reviewing files that changed from the base of the PR and between c536f06 and 48ea65a.
Files ignored due to path filters: 1
pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing: 4
package.json
pnpm-workspace.yaml
server/utils/content/instances.ts
utils/factory.ts
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.
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
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.
atinux
changed the title
Upgrades
comark-contentfrom 0.4.3 to 0.5.1, the version the upcoming Nuxt Content v4 module depends on. 0.5 removed thecomark-content/sources/githubsource, so nuxt.com's GitHub-backed content instances (site, docs, cli, examples, module docs) now read GitHub through the genericforgesource.This branch started as an exploration of moving nuxt.com onto the Nuxt Content v4 module (nuxt/content-v4-temp#37). The module can't serve nuxt.com yet: every instance reads a repository at the commit its branch points to, and
vercel.jsonskips deploys for content-only pushes, so evensitecan't ship with the build. That attempt is reverted in this branch, and its findings (six gaps in the module) are on nuxt/content-v4-temp#37. What's left here is only the dependency upgrade.What changed
package.json:comark-content^0.4.3 → ^0.5.1, andforges^0.3.2 as a new direct dependency.utils/factory.ts:github({ repo, branch, path, token, ttl })becomesforge({ provider: github({ auth }), repo, ref, path }), withgithubfromforges/github. The token is passed as forge auth when one is configured.server/utils/content/instances.ts: the source option type comes fromcomark-content/sources/forgeinstead ofsources/github.pnpm-workspace.yaml: thecomarkoverride comment no longer names comark-content, which accepts comark 0.9 since 0.5.No app, page, webhook, snapshot, search or l10n code changes.
Evidence
pnpm install --frozen-lockfilepnpm why comark→ 1 version (0.9.0);pnpm why comark-content→ 1 version (0.5.1)pnpm lint,pnpm test:typespnpm vitest run --project unit/--project nuxtpnpm buildforge:site snapshot 350a1a4: 1823 kB, plus examples, docs:4.x, cli:4.x and 6 module docsThe built server (
node .output/server/index.mjs, with a GitHub token) returned 200 for/docs/4.x/getting-started/introduction,/blog/v4,/raw/blog/v4.md,/deploy/vercel,/docs/4.x/api/commands/dev,/llms.txt,/api/navigation/4.xand/fr/docs/4.x/getting-started/introduction, and the blog post renders normally.Worth checking before merging
githubsource cached each read for 24 hours (ttl);forgehas no equivalent option. Reads go throughwithRef(sha), so they're for immutable commits, and parsed results still go through each instance's cache driver, but GitHub API usage under production traffic hasn't been watched on Vercel. Worth a look at the Vercel preview's logs, or after deploying.main's history to this one change.ELI5
nuxt.com reads its docs and blog from GitHub through a library called comark-content. This updates that library to its newest version, which reads GitHub in a slightly different way. The site works the same.