Commit 30b0d72
committed
build(eval-author)!: stop shipping the skills in nemo-platform[all]
The package has no entry points and no importable code, so bundling it into the
platform distribution shipped files that nothing can discover. `nemo skills list`
reads the `nemo.skills` registry and these skills are not registered there yet, so
a customer installing nemo-platform[all] received two SKILL.md files reachable only
by knowing a path inside the wheel. Installing them into service images through
enabled-plugins had the same problem.
Removes the [tool.bundle-package] entry, which is what generated the
nemo-eval-author-plugin extra along with its membership in the plugins and all
extras, and drops the package from enabled-plugins. Regenerating cleared every
eval-author reference out of the published wrapper.
The package stays a uv workspace member, so uv sync --all-packages still installs
it for development and the contract test still runs. Bundle it again when the
skills register under nemo.skills and a distribution has something to expose.
Signed-off-by: Alec Khoury <akhoury@nvidia.com>1 parent 2d5c272 commit 30b0d72
3 files changed
Lines changed: 5 additions & 27 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
291 | 291 | | |
292 | 292 | | |
293 | 293 | | |
294 | | - | |
295 | | - | |
296 | | - | |
297 | | - | |
298 | | - | |
299 | | - | |
300 | 294 | | |
301 | 295 | | |
302 | 296 | | |
| |||
484 | 478 | | |
485 | 479 | | |
486 | 480 | | |
487 | | - | |
488 | 481 | | |
489 | 482 | | |
490 | 483 | | |
| |||
723 | 716 | | |
724 | 717 | | |
725 | 718 | | |
726 | | - | |
727 | | - | |
728 | | - | |
729 | | - | |
730 | | - | |
731 | | - | |
| 719 | + | |
| 720 | + | |
| 721 | + | |
| 722 | + | |
732 | 723 | | |
733 | 724 | | |
734 | 725 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
187 | 187 | | |
188 | 188 | | |
189 | 189 | | |
190 | | - | |
191 | 190 | | |
192 | 191 | | |
193 | 192 | | |
| |||
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments