Skip to content

Conversation

@atinux
Copy link
Member

@atinux atinux commented Dec 11, 2025

Following #3855 so both websites links to each others + knowing the current major version from the header.

CleanShot 2025-12-11 at 01 05 33@2x

@atinux atinux requested a review from pi0 as a code owner December 11, 2025 00:05
@vercel
Copy link

vercel bot commented Dec 11, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
nitro.build Ready Ready Preview Comment Dec 11, 2025 0:06am

@coderabbitai
Copy link

coderabbitai bot commented Dec 11, 2025

📝 Walkthrough

Walkthrough

Added a versions configuration array to docs/.config/docs.yaml containing entries for v3 (alpha) and v2. Updated the undocs devDependency in docs/package.json from ^0.4.10 to ^0.4.11.

Changes

Cohort / File(s) Summary
Documentation Configuration
docs/.config/docs.yaml
Added versions array with two entries: "v3 (alpha)" marked as active and "v2" with link to https://nitro.build
Package Dependencies
docs/package.json
Updated undocs devDependency from ^0.4.10 to ^0.4.11

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Both changes are straightforward additions and dependency version bumps with no logic or structural complexity
  • Configuration entry addition requires only verification of format and links
  • Dependency update is purely mechanical with no breaking changes indicated

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title follows conventional commits format with 'docs' scope and 'v3' subject, clearly summarizing the main change of adding a versions menu.
Description check ✅ Passed The description is directly related to the changeset, referencing PR #3855 and explaining the purpose of adding the versions menu.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs-v3/versions-menu

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 11, 2025

Open in StackBlitz

npm i https://pkg.pr.new/nitrojs/nitro@3856

commit: 7d83784

@pi0 pi0 merged commit afcf27a into main Dec 11, 2025
11 of 12 checks passed
@pi0 pi0 deleted the docs-v3/versions-menu branch December 11, 2025 00:09
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0efa641 and 7d83784.

⛔ Files ignored due to path filters (1)
  • docs/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • docs/.config/docs.yaml (1 hunks)
  • docs/package.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: tests-rolldown (windows-latest)
  • GitHub Check: tests-rollup (windows-latest)
  • GitHub Check: tests-rollup (ubuntu-latest)
🔇 Additional comments (1)
docs/.config/docs.yaml (1)

15-19: The versions array structure is correct and matches the undocs configuration schema. The properties label, active, and to are all supported in undocs v0.4.11, and their usage here is proper: label for display text, active to mark v3 as the current version, and to to link v2 to the legacy docs at https://nitro.build.

"devDependencies": {
"shaders": "^2.0.674",
"undocs": "^0.4.10"
"undocs": "^0.4.11"
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

undocs 0.4.11 release changelog features versions menu

💡 Result:

Minetest 0.4.11 — release date: December 24, 2014. Key changelog items (high‑level): added mapgen v5 and enable_build_where_you_stand; inventory right‑click drag/drop; various visual/UI changes (video‑driver selection in settings, node highlighting, configurable selection‑box width, in‑game key‑change menu, removed screenshot alpha, etc.); gameplay tweaks and tweaks to dropped items/third‑person view; many other minor fixes and improvements. (olddev.minetest.org)

Citations:


🌐 Web query:

undocs npm package version 0.4.11

💡 Result:

I can't find an official npm release named undocs@0.4.11. The public undocs package latest listed is v0.4.10, while a "undocs‑nightly" package has a 0.4.11-... nightly build (0.4.11-20250925-130907-fa6d5d2). Sources: [Socket (undocs)] [1], [Socket (undocs‑nightly)] [2].

If you want, I can fetch the exact registry metadata/tarball info for a specific package name.


Remove or clarify undocs version reference — 0.4.11 does not exist as an official release.

The npm package undocs@0.4.11 is not available in the public npm registry. The latest official release is v0.4.10. Updating to ^0.4.11 will cause installation failures. Either revert to ^0.4.10 or switch to the undocs-nightly package if nightly builds are intended.

🤖 Prompt for AI Agents
In docs/package.json around line 9, the dependency "undocs": "^0.4.11"
references a non-existent release and will break installs; change it to a valid
version or the intended package: either update the version to "^0.4.10" (the
latest official release) or replace the dependency with "undocs-nightly" (or the
correct nightly package name) if nightly builds were intended, and run npm
install / yarn install to verify resolution.

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.

2 participants