Skip to content

chore: replace latest ranges with caret ranges #782

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
danielroe merged 1 commit into from
Aug 6, 2026
+1 −1
Merged

chore: replace latest ranges with caret ranges #782

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion example/playground/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
},
"dependencies": {
"my-module": "workspace:*",
"nuxt": "latest"
"nuxt": "^4.5.1"

@coderabbitai coderabbitai Bot Aug 6, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

rg -n -A12 -B3 'nuxt|specifier' example/playground/package.json pnpm-lock.yaml

Repository: nuxt/module-builder

Length of output: 50375

Align the manifest range with the lockfile range.

example/playground/package.json:9 uses ^4.5.1, while pnpm-lock.yaml records the playground Nuxt importer as specifier: ~4.5.1. If the caret range is intentional, regenerate the lockfile; if only patch-level updates are intended, change the manifest to ~4.5.1.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@example/playground/package.json` at line 9, Align the Nuxt dependency range
in the playground manifest with the lockfile: update the "nuxt" entry to ~4.5.1
for patch-level updates, or retain ^4.5.1 only after regenerating pnpm-lock.yaml
so its importer specifier matches.

},
"devDependencies": {
"typescript": "^5.9.3",
Expand Down
Loading