fix(release): use directory-relative turbo filter in prepack scripts

[antfubot]

Problem

The nightly release job (Release Nightly step in CI) has been failing:

turbo run build --filter=@nuxt/devtools
x No package found with name '@nuxt/devtools' in workspace

https://github.com/nuxt/devtools/actions/runs/32479282934/job/96761993765

Cause

scripts/bump-nightly.ts renames every publishable package (e.g.
@nuxt/devtools -> @nuxt/devtools-nightly) before
scripts/release-nightly.sh runs pnpm publish in each package
directory. pnpm publish triggers each package's prepack script,
which called turbo run build --filter=@nuxt/devtools (and the
equivalent hardcoded name for the other three packages) — a filter
that stopped matching anything as soon as the package was renamed.

This was introduced when prepack was switched from pnpm build to
a turbo-filtered build in #1071.

Fix

Use turbo's directory-relative filter, --filter=., in all four
prepack scripts. It resolves to whichever package lives in the
current directory (and its dependencies), independent of the name
field, so it keeps working after the nightly rename.

Verified locally that --filter=. produces the same dependency graph
as the previous name-based filter for all four packages, and that it
keeps resolving correctly after simulating the nightly rename (whereas
the old name-based filter fails, reproducing the CI error).

---

This PR was created with the help of an agent.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d8466963-ba0e-4658-a664-b68f36459055

📥 Commits

Reviewing files that changed from the base of the PR and between 40f22f2 and b3079d8.

📒 Files selected for processing (4)

• packages/devtools-assets/package.json
• packages/devtools-kit/package.json
• packages/devtools-ui-kit/package.json
• packages/devtools/package.json

Included review availability: Your plan provides up to 8 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

Four package prepack scripts now run turbo run build --filter=.. The scripts previously filtered Turbo by each package name.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk:⚪ Minimal · up to b3079

This localized change makes prepack builds continue to target the current package after nightly renaming, with no actionable merge-blocking risk remaining beyond normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: replacing hardcoded package filters with the directory-relative Turbo filter in prepack scripts.
Description check	✅ Passed	The description explains the nightly release failure, its cause, and the fix across all four package prepack scripts.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (4 skipped: 4 unsupported.)
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}