fix: robust GitHub Actions publishing workflow#4
Conversation
- Fixed `publish.yml` to handle initial package publications (first-time publishing). - Added version-check protection to avoid redundant publish attempts. - Added `NPM_TOKEN` verification step for better error debugging. - Ensured all packages have `publishConfig` for public NPM registry. - Standardized package naming and synchronization for CI/CD. Co-authored-by: codedbytahir <200578194+codedbytahir@users.noreply.github.com>
|
Caution Review failedThe pull request is closed. 📝 WalkthroughWalkthroughThe pull request updates the project's release automation and documentation practices. The CI workflow comment is clarified, the publish workflow gains NPM token verification and conditional publishing logic to prevent redundant releases, the main README is rewritten with CLI-first onboarding guidance, and the create-motionforge package adds explicit publish configuration. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
✨ Finishing touches🧪 Generate unit tests (beta)
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 |
publish.ymlto handle initial package publications (first-time publishing).NPM_TOKENverification step for better error debugging.publishConfigfor public NPM registry.Summary by CodeRabbit