| name | maintain-packaging |
| description | Maintain NeMo Relay package metadata, module paths, generated artifacts, and release-facing build surfaces |
| author | NVIDIA Corporation and Affiliates |
| license | Apache-2.0 |
Maintain 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.toml package 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.json and package-lock.json
- Node package metadata in
crates/node/package.json
- FFI header and library naming
- CI workflows, install commands, and example commands
justfile build, test, clean, version, and package recipes for plugin crates
and packages- Release tags, release-note surfaces, and registry-facing version translation
Checklist
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
