菜单
Prepare a NeMo Relay code freeze by creating the release branch, updating nightly alpha branch config, bumping main to the next version, and opening the required PR
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Compare NeMo Relay release branches and draft or update the documentation-site release notes. Use when preparing a release-notes update under docs/about-nemo-relay/release-notes, reviewing release-to-release changes, or gathering evidence for a current release summary.
Contribute documentation or example changes that stay aligned with NeMo Relay public behavior
Build and package reusable NeMo Relay runtime behavior as a config-activated plugin with validation and rollback-safe registration
Add or change a public NeMo Relay API surface across the core runtime and every affected binding
Maintain or extend NeMo Relay observability surfaces across ATIF, OpenTelemetry, and OpenInference
Maintain or extend the NeMo Relay adaptive surface across config, plugins, docs, and bindings; use this when users still say optimizer
| name | prepare-code-freeze |
| description | Prepare a NeMo Relay code freeze by creating the release branch, updating nightly alpha branch config, bumping main to the next version, and opening the required PR |
| author | NVIDIA Corporation and Affiliates |
| license | Apache-2.0 |
Use this skill when the user asks to start, prepare, or automate a NeMo Relay code freeze.
Use update-project-version for version bump semantics and prepare-pr before
opening the PR.
This workflow assumes upstream is the NVIDIA repository remote
(NVIDIA/NeMo-Relay). The origin remote can be a maintainer's personal fork.
Confirm or infer the target release version from upstream/main:Cargo.toml.
Derive the release branch as release/<major>.<minor>.
Prompt for <next-version> if the user did not provide it. This is the
version that main moves to after the release branch is cut.
Fetch the latest main and create the release branch from upstream/main:
git fetch upstream main
git branch release/<major>.<minor> upstream/main
git push upstream release/<major>.<minor>
If the remote release branch already exists, verify it points where expected before continuing.
Create a PR branch from latest upstream/main, for example
docs/code-freeze-<major>.<minor>.
Update .github/nightly-alpha-branches.yaml to include the new release
branch.
Run just set-version <next-version> to bump all release-versioned package
surfaces on main.
Search documentation source for references to the old version and update
current-version install commands, package examples, and configuration
examples to <next-version> where appropriate:
rg -n '<old-version>' README.md docs fern --glob '!docs/_build/**' || true
Review matches before changing them. Leave intentional historical references alone, such as release notes, changelogs, generated build output, and third-party dependency attribution entries.
Validate with targeted checks:
ruby -e 'require "yaml"; YAML.load_file(".github/nightly-alpha-branches.yaml"); YAML.load_file(".github/workflows/nightly-alpha-tag.yaml")'
just set-version <next-version>
rg -n '<old-version>' README.md docs fern --glob '!docs/_build/**' || true
git diff --check
Any remaining documentation matches for <old-version> should be intentional
and called out in the PR description.
Open a PR targeting main using .github/pull_request_template.md. The PR
must mention:
just set-version <next-version> bumprelease/* branchmain.