fix(repo): include vercel-ai-exporter in workspace/build so package is published#1094
fix(repo): include vercel-ai-exporter in workspace/build so package is published#1094pandego wants to merge 1 commit intoVoltAgent:mainfrom
Conversation
🦋 Changeset detectedLatest commit: 89c35d9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
No actionable comments were generated in the recent review. 🎉 📝 WalkthroughWalkthroughThe PR removes Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. 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. Comment |
Summary
This PR fixes the packaging pipeline so
@voltagent/vercel-ai-exporteris actually built and included in release workflows.Root cause
pnpm-workspace.yamlexplicitly excludedpackages/vercel-ai-exporter@voltagent/vercel-ai-exporterThat combination can lead to publishing the package without generated
distartifacts.Changes
!packages/vercel-ai-exporterfrompnpm-workspace.yamlbuildandbuild:allscripts (no exporter-specific ignore)@voltagent/vercel-ai-exporterpatch releaseValidation
pnpm --ignore-scriptsand package build path checksFixes #1024
Summary by CodeRabbit