Repository navigation
Conversation
Codex Review Summary: ❌ FailedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Important
Hold the merge until the default frozen install passes. The current CI run fails before any build or tests run.
Approach: Moving the docs from preview tarballs to the published ViteHub release is the right change, and it lets the workspace restore pnpm’s default handling of exotic transitive dependencies.
Reviewed changes
- Docs dependencies:
@vite-hub/contentand its four ViteHub dependencies now resolve to npm0.3.1. The lockfile also updates the Nuxt CLI nightly while keeping Nuxt itself at the same version. - Workspace policy: The preview-only
blockExoticSubdeps: falseoverride is removed. - Verification: With local exceptions for only the five new package versions,
pnpm docs:generateprerendered 98 routes and emitted the Worker config. A live deploy was not run.
⚠️ P1 — Class: release-age gate rejects the frozen install
As the PR description anticipates, the unmodified pnpm install --frozen-lockfile exits with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION for all five new @vite-hub/*@0.3.1 entries. I reproduced the CI failure; the latest publish timestamp reported by pnpm puts the end of the one-day window at 15:34:12 UTC on November 20.
Technical details
# Frozen-install release-age gate
## Affected sites
- `docs/package.json:12` and `pnpm-lock.yaml:187` — the docs importer selects the newly published release and its four locked ViteHub dependencies.
- `.github/workflows/ci.yml:33` — the root frozen install checks the whole workspace, so jobs that do not build the docs fail too.
## Required outcome
- Rerun normal CI after 15:35 UTC on November 20, 2026, and confirm the frozen install passes before merging. No policy exception is needed if you wait.gpt-6.2-sol(high) | 𝕏

The docs site ran
@vite-hub/contentfrom a ViteHub preview build on pkg.pr.new (db9f307, 2026-11-17). ViteHub 0.3.1 is now on npm, so this PR moves@vite-hub/contentto^0.3.1. The pages come out the same. Merging deploys: Workers Builds deploysmainto tiny.onmax.me.docs/package.jsonnow says^0.3.1. The lockfile has one copy of each ViteHub package it installs (Content, Blob, Forge, Runtime, Source), all 0.3.1, and no pkg.pr.new entries.blockExoticSubdeps: falseis gone. It was there only because pkg.pr.new tarballs depend on other tarball URLs.@nuxt/cli-nightly.The site needed no code change. The breaking ViteHub changes between
db9f307and 0.3.1 are new error codes for Content setup errors and for the causes ofCONTENT_R0006andCONTENT_R0008. The site reads no error codes (onError: "throw").Verified on this branch, Node 24 on Linux:
pnpm install --frozen-lockfilepasses.pnpm docs:generateonmainand on this branch prerender 98 routes each. Then I compareddocs/dist/public: the same 115 files outside_nuxt/, the same visible text on all 24 pages, and every.mdcopy,search.json,llms.txtand_headersbyte-identical. The only other differences are the build time and build ID in the_payload.jsonfiles.wrangler@4.158.0 dev -c docs/dist/server/wrangler.json:/,/tinyaml/guide/getting-started/,/tinylinkify/compatibility/,/search.json,/llms.txt,/index.mdand/tinyaml/guide/api.mdanswer 200 with the right content types.Accept: text/markdownon/answers Markdown,/nope/answers 404, andHost: tinyaml.onmax.megets a 301 tohttps://tiny.onmax.me/guide/.pnpm docs:devstill fails with "Unrecognized import attributes specified" (pages 404,/search.json500).mainfails the same way, so this PR doesn't change it.ViteHub 0.3.1 came out on 2026-11-19 at 15:42 UTC. Until 2026-11-20 at about 15:40 UTC, pnpm's default one-day
minimumReleaseAgerejects it, also on a frozen install. Workers Builds and CI fail before then, so merge or rerun after that time. I checked the install locally with the gate turned off for@vite-hub/*only.Not checked: a deploy.
Prepared with Claude Opus 5.5 in Claude Code.