Repository navigation
fix: scope maintainer skill identity to the owning package - #313
Conversation
🦋 Changeset detectedLatest commit: e1dc69d 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 |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 17 minutes. View limit detailsLimit details: You’ve used all 2 included reviews currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (10)
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 |
|
View your CI Pipeline Execution ↗ for commit e5fb2ee
☁️ Nx Cloud last updated this comment at |
commit: |
🎯 Changes
intent maintainertreated a skill name as unique across the whole repository. In a monorepo where two packages each register a skill with the same name, every maintainer command stopped withDuplicate skill identity or path. TanStack Table hasgetting-started,table-state, andmigrate-v8-to-v9in several adapter packages, somaintainer status,check, andsynccould not run there.A skill name is now unique within its owning package.
maintainer add. The same name can be registered in a second package.requiresrefers to a skill in the same package. A skill in another package is named as<package>#<skill>. A bare name that only exists in another package is now reported bysyncandcheck.maintainer remove <name>. Accepts--package <directory>. When more than one package registers the name and no package is given, the command lists the packages.domain_map.yamlhas several entries with the same slug,synccompares a skill with the entry in its own domain.maintainer setup. Existing skills with the same name in different packages are both registered. Two unregistered skills with the same name in one package are still skipped.