Skip to content
Skills Library
DevOps & cloud · Automation

update-project-version

/update-project-version

Perform a NeMo Relay project release-version change across project-owned manifests, dependencies, lockfiles, and generated attribution surfaces while keeping just set-version coverage complete. Do not use for dependency-only updates or adding a package when no project version bump is requested.

Repository
nemo-relay ↗
Licence
Apache-2.0
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Perform a NeMo Relay project release-version change across project-owned manifests, dependencies, lockfiles, and generated attribution surfaces while keeping just set-version coverage complete. Do not use for dependency-only updates or adding a package when no project version bump is requested.

Original author description

Perform a NeMo Relay project release-version change across project-owned manifests, dependencies, lockfiles, and generated attribution surfaces while keeping just set-version coverage complete. Do not use for dependency-only updates or adding a package when no project version bump is requested.

How it works

  1. Invariants
  2. Workflow
  3. Verification
  4. References
Original SKILL.md headings · 61 lines, 380 words
SKILL.md preview
---
name: update-project-version
description: Perform a NeMo Relay project release-version change across project-owned manifests, dependencies, lockfiles, and generated attribution surfaces while keeping just set-version coverage complete. Do not use for dependency-only updates or adding a package when no project version bump is requested.
license: Apache-2.0
---

# Update Project Version

Use this skill for project release-version changes, including prerelease and
build-metadata variants.

## Invariants

- `Cargo.toml` `[workspace.package].version` is the Rust source of truth.
- `just set-version <version>` is the single repository entrypoint for updating
  normal project-version surfaces. Do not hand-edit its existing targets.
- Every new package or plugin that participates in the unified NeMo Relay
  release, plus its project-version dependencies and lockfile entries, must be
  covered by the version automation. If a value does not derive automatically,
  update the automation in the same change that introduces it.
- Python surfaces use PEP 440 translations where required; Cargo, npm, and
  plugin manifests use the repository SemVer form.

## Workflow

Use this sequence:

1. Read the current version from `Cargo.toml` and choose the exact target.
2. Compare project-owned package/workspace members and plugin manifests with
   the helpers called by `set_project_version`, paying particular attention to
   recent or in-scope additions. A new manifest, publishable package, internal
   dependency pinned to the project version, or lockfile package entry is a
   signal that `just set-version` may need to change.
3. Run `just set-version <version>`.
4. Review the diff, then search tracked Cargo, Python, npm, lockfile, and plugin
   manifests for the exact old version. Classify matches rather than replacing
   them blindly: third-party pins and examples can legitimately match.
5. If a project-owned release surface remains on the old version, update the
   appropriate helper and rerun `just set-version <version>`. Read
   `references/version-automation.md` only when the version topology or helper
   implementation changes.
6. Refresh lockfiles or attribution files only when their versioned inputs
   changed. Do not run language suites for a metadata-only bump.

## Verification

Before handoff, verify:

- Confirm every project-owned manifest version and internal dependency resolves
  to the target SemVer or its expected PEP 440 translation, and that unrelated
  versions did not change.
- Rerun `just set-version <version>` when automation changed; it should be
  idempotent and report no missing expected fields.
- Use focused checks for edited helper code and targeted packaging or generated
  output checks only for surfaces affected by the bump.

Temporary versions produced by packaging recipes are not the canonical project
version unless the release workflow explicitly requires that exact suffix.

## References

- `Cargo.toml`
- `justfile`
- `references/version-automation.md` — only for adding, removing, or debugging
  a versioned surface or version helper
Files in this package (2)
  • SKILL.md 3 KB
  • references/version-automation.md 3 KB

Versions

RepositoryScoreLicence
This page · nvidia/nemo-relay100Apache-2.0
nvidia/nemo-fabric100Apache-2.0

Database snapshot: 13.11.2026 · package version 871b6724afc9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100maintain-packaging
    Add or change NeMo Relay packages, package metadata, module paths, generated artifacts, registry output, or release-facing build surfaces, including registering new unified-release surfaces with version automation. Do not use for a standalone project version bump, ordinary source builds, or tests.
  • 100prepare-code-freeze
    Execute a requested NeMo Relay code freeze by cutting a release branch, updating nightly alpha configuration, bumping main, and preparing the required PR. Do not use for an ordinary version bump or release-note draft.
  • 100release
    Prepare a change in this repo (pi-plugin-cc) for release. Picks the Semantic Versioning bump against the default branch, sets the version in package.json, package-lock.json, plugin.json, and marketplace.json with `npm run bump-version`, writes the CHANGELOG.md entry under that…
  • 100release
    Perform a full versioned release — bump version, draft release notes, commit, tag, push, and create the GitHub release page. Reads `.claude/project.yaml` for the project's release-context and version-bump helpers; the skill text is universal, the helpers are project-supplied.…
  • 100bump-version
    Use when asked to bump the version, prepare or create a release, update the version number, or determine a semantic version increment from recent commits.
  • 100version-release
    Use when bumping version, creating a release tag, or pushing a version tag. Triggers on "version up", "release", "tag push", "bump version".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.