Skip to content

chore: run on ViteHub 0.3.1 - #40

Open
onmax wants to merge 1 commit into
mainfrom
chore/vitehub-0.3.1
Open

onmax wants to merge 1 commit into
mainfrom
chore/vitehub-0.3.1

Conversation

@onmax

@onmax onmax commented Nov 20, 2026

Copy link
Copy Markdown
Owner

The docs site ran @vite-hub/content from 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/content to ^0.3.1. The pages come out the same. Merging deploys: Workers Builds deploys main to tiny.onmax.me.

  • docs/package.json now 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: false is gone. It was there only because pkg.pr.new tarballs depend on other tarball URLs.
  • The Nuxt nightly stays at the locked 5.0.0-2611081128-d54cab9, and the library packages' lockfile entries don't change. The only other lockfile change is @nuxt/cli-nightly.

The site needed no code change. The breaking ViteHub changes between db9f307 and 0.3.1 are new error codes for Content setup errors and for the causes of CONTENT_R0006 and CONTENT_R0008. The site reads no error codes (onError: "throw").

Verified on this branch, Node 24 on Linux:

  • pnpm install --frozen-lockfile passes.
  • pnpm docs:generate on main and on this branch prerender 98 routes each. Then I compared docs/dist/public: the same 115 files outside _nuxt/, the same visible text on all 24 pages, and every .md copy, search.json, llms.txt and _headers byte-identical. The only other differences are the build time and build ID in the _payload.json files.
  • wrangler@4.158.0 dev -c docs/dist/server/wrangler.json: /, /tinyaml/guide/getting-started/, /tinylinkify/compatibility/, /search.json, /llms.txt, /index.md and /tinyaml/guide/api.md answer 200 with the right content types. Accept: text/markdown on / answers Markdown, /nope/ answers 404, and Host: tinyaml.onmax.me gets a 301 to https://tiny.onmax.me/guide/.

pnpm docs:dev still fails with "Unrecognized import attributes specified" (pages 404, /search.json 500). main fails 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 minimumReleaseAge rejects 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.

@chatgpt-codex-connector

Copy link
Copy Markdown
Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ❌ Failed 2026-11-20T10:30:24.785549Z
We couldn’t complete this review. Comment @codex review to try again.
ff993ed PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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/content and its four ViteHub dependencies now resolve to npm 0.3.1. The lockfile also updates the Nuxt CLI nightly while keeping Nuxt itself at the same version.
  • Workspace policy: The preview-only blockExoticSubdeps: false override is removed.
  • Verification: With local exceptions for only the five new package versions, pnpm docs:generate prerendered 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.

Pullfrog  | Fix it ➔ | View workflow run | Using gpt-6.2-sol(high) | 𝕏

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant