maintain-packaging
bởi nvidia
Duy trì siêu dữ liệu gói NeMo Relay, đường dẫn module, các tạo phẩm đã sinh và bề mặt xây dựng hướng tới phát hành
npx skills add https://github.com/nvidia/nemo-relay --skill maintain-packagingMaintain Release And Packaging Surfaces
Companion Guidance
Use karpathy-guidelines alongside this skill for implementation or review
work. Keep changes scoped, surface assumptions, and define focused validation
before editing.
Use this skill when a change affects how NeMo Relay is built, packaged, named, or consumed outside the source tree.
Audit Areas
- Rust
Cargo.tomlpackage names and workspace metadata - Python packaging in
pyproject.toml - Python worker plugin SDK packaging in
python/plugin/pyproject.toml - Go module path in
go/nemo_relay/go.mod - Node workspace metadata in root
package.jsonandpackage-lock.json - Node package metadata in
crates/node/package.json - FFI header and library naming
- CI workflows, install commands, and example commands
justfilebuild, test, clean, version, and package recipes for plugin crates and packages- Release tags, release-note surfaces, and registry-facing version translation
Checklist
- Package names, import paths, and module names are internally consistent
- Generated artifacts still land where downstream consumers expect
- Docs and examples use the current install/import/build commands
- CI references the same package names as local workflows
- Public packaging changes are reflected in release-facing docs
-
nemo-relay-pluginRust and Python packages track the project SemVer policy and Python wheels use valid PEP 440 translation - Release tags still use raw SemVer without a leading
v - Release history and release notes still point to GitHub Releases, not
CHANGELOG.mdor docs pages
References
pyproject.tomlpython/plugin/pyproject.tomlgo/nemo_relay/go.modpackage.jsonpackage-lock.jsoncrates/node/package.jsonRELEASING.md.github/workflows/ci_python.yml.github/workflows/ci.yaml.gitlab-ci.ymlmaintain-dynamic-plugins