create-rc-tag
Create and push a signed, annotated NeMo Fabric release-candidate tag from its validated release branch. Use when cutting an RC tag; not for code freezes or stable release tags.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-12
- Stars
- ★ 4
- Forks
- 0
01 前言 Front Matter
- name
- create-rc-tag
- author
- NVIDIA Corporation and Affiliates
- license
- Apache-2.0
- description
- Create and push a signed, annotated NeMo Fabric release-candidate tag from its validated release branch. Use when cutting an RC tag; not for code freezes or stable release tags.
03 SKILL.md 正文
Create an RC Tag
Create the tag only after the release branch has been created.
Determine the version
Require the user to provide the stable release version in either
<major>.<minor> or <major>.<minor>.<patch> form. Treat a two-component
version as <major>.<minor>.0. Do not infer the version from Cargo.toml or
a branch name, and do not edit Cargo.toml while cutting the tag. Normalize
the supplied version into RELEASE_BASE_VERSION:
RELEASE_VERSION_INPUT="<user-provided-major.minor[.patch]>"
if [[ "${RELEASE_VERSION_INPUT}" =~ ^[0-9]+\.[0-9]+$ ]]; then
RELEASE_BASE_VERSION="${RELEASE_VERSION_INPUT}.0"
elif [[ "${RELEASE_VERSION_INPUT}" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
RELEASE_BASE_VERSION="${RELEASE_VERSION_INPUT}"
else
echo "Error: release version must be <major>.<minor> or <major>.<minor>.<patch>" >&2
exit 1
fi
RELEASE_BRANCH="release/$(printf '%s' "${RELEASE_BASE_VERSION}" | cut -d. -f1,2)"
if ! git ls-remote --exit-code --heads upstream "refs/heads/${RELEASE_BRANCH}" >/dev/null; then
echo "Error: remote release branch ${RELEASE_BRANCH} does not exist on upstream" >&2
exit 1
fi
git fetch upstream "${RELEASE_BRANCH}" --tags
If the user provides an RC number, use it. Otherwise, after fetching tags,
select one greater than the largest numeric RC suffix for this exact base
version. Start at 1 when none exists:
LAST_RC_NUM="$(
git tag --list "v${RELEASE_BASE_VERSION}-rc.*" |
awk -v prefix="v${RELEASE_BASE_VERSION}-rc." '
index($0, prefix) == 1 {
suffix = substr($0, length(prefix) + 1)
if (suffix ~ /^[0-9]+$/ && suffix + 0 > max) max = suffix + 0
}
END { if (max) print max }
'
)"
RC_NUM="${LAST_RC_NUM:+$((LAST_RC_NUM + 1))}"
RC_NUM="${RC_NUM:-1}"
RELEASE_VERSION="${RELEASE_BASE_VERSION}-rc.${RC_NUM}"
RELEASE_TAG="v${RELEASE_VERSION}"
Use an explicitly supplied RC number only after checking it is a positive integer and that its remote tag does not already exist.
Create and verify the tag
Assume upstream is the NVIDIA repository remote. Preserve user changes: do
not stash, discard, or switch away from a dirty worktree. The preceding remote
branch check must succeed before switching to the release branch. Require its
checked-out commit to equal the upstream branch before tagging:
Run the remaining commands in one noninteractive Bash session. Record the user's original checkout and install this exit trap before switching branches. The trap returns to the original named branch (or detached commit) after a successful tag or any error, but only if this workflow changed the checkout.
set -euo pipefail
ORIGINAL_BRANCH="$(git branch --show-current)"
ORIGINAL_HEAD="$(git rev-parse --verify HEAD)"
CHECKOUT_CHANGED=false
restore_checkout() {
local outcome=$?
trap - EXIT
if [[ "${CHECKOUT_CHANGED}" == true ]]; then
if [[ -n "${ORIGINAL_BRANCH}" ]]; then
git switch "${ORIGINAL_BRANCH}" || outcome=1
else
git switch --detach "${ORIGINAL_HEAD}" || outcome=1
fi
fi
exit "${outcome}"
}
trap restore_checkout EXIT
if [[ "${ORIGINAL_BRANCH}" != "${RELEASE_BRANCH}" ]]; then
git switch "${RELEASE_BRANCH}"
CHECKOUT_CHANGED=true
fi
git pull --ff-only upstream "${RELEASE_BRANCH}"
test -z "$(git status --porcelain)"
RELEASE_SHA="$(git rev-parse HEAD)"
REMOTE_RELEASE_SHA="$(git rev-parse "upstream/${RELEASE_BRANCH}^{commit}")"
test "${RELEASE_SHA}" = "${REMOTE_RELEASE_SHA}"
test "$(just normalize-release-tag "${RELEASE_TAG}")" = "${RELEASE_VERSION}"
CURRENT_VERSION="$(python -c "import tomllib; print(tomllib.load(open('Cargo.toml', 'rb'))['workspace']['package']['version'])")"
test "${CURRENT_VERSION}" = "${RELEASE_BASE_VERSION}"
if git ls-remote --exit-code --tags upstream "refs/tags/${RELEASE_TAG}" >/dev/null; then
echo "Error: remote tag ${RELEASE_TAG} already exists" >&2
exit 1
fi
git tag -s -a \
-m "NVIDIA NeMo Fabric ${RELEASE_VERSION}" \
"${RELEASE_TAG}" \
"${RELEASE_SHA}"
git tag -v "${RELEASE_TAG}"
git show "${RELEASE_TAG}"
test "$(git rev-parse "${RELEASE_TAG}^{commit}")" = "${RELEASE_SHA}"
git push upstream "refs/tags/${RELEASE_TAG}"
Stop on any failed check. Do not force-update, replace, or delete an existing local or remote tag.
04 同仓库更多 Skills
agentic-ecology-ui
Guidelines and templates for creating a generic web UI to visualize, rank, filter, and annotate vector databases. The UI has a hierarchical structure covering database selection, label selection/definition, ranking/filtering configuration, and row visualization/annotation. Use when building, serving, or adapting an interactive web UI for Hoplite vector databases.
agentic-ecology-init
Initializes a local uv-managed project directory for agentic ecology workloads. Sets up Python dependencies using reference pyproject.toml and uv.lock, configures workspace rules, and ensures Agentic Ecology skills are discoverable. Use when initializing a new project workspace or bootstrapping a clean environment.
agentic-ecology-camera-traps
Provides capabilities to run SpeciesNet detector and classifier on camera trap images, extract crop-level feature embeddings, and populate a Hoplite vector database for downstream search and agile modeling. Use when ingesting camera trap images, classifying wildlife photos, or indexing camera trap data.
agentic-ecology-bioacoustics
Provides bioacoustic analysis capabilities for ecologists and researchers using the perch-hoplite Python package. A typical use case is to use agile modeling to bootstrap the creation and deployment of a bespoke detector for targeted species on an existing collection of passive acoustic monitoring recordings. Use when processing and annotating audio recordings for bioacoustic applications.
sample-skill
Sample skill used by agent-env integration tests. Exercises SKILL.md parsing plus supporting scripts and references.
simready-foundation-validate-foundation-change
Use for auditing SimReady requirement, validator, feature, profile, adapter, test, and skill consistency.