check-release-deployments
Verify whether a tagged NeMo Fabric release is deployed to crates.io, PyPI, and npm. Use when checking publication status for a specific release tag; not for publishing packages or creating tags.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 75
- Forks
- 47
01 前言 Front Matter
- name
- check-release-deployments
- author
- NVIDIA Corporation and Affiliates
- license
- Apache-2.0
- description
- Verify whether a tagged NeMo Fabric release is deployed to crates.io, PyPI, and npm. Use when checking publication status for a specific release tag; not for publishing packages or creating tags.
02 资源文件 1
03 SKILL.md 正文
Check Release Deployments
Require the release tag as input. Do not infer the tag from the current branch, Git history, or package metadata.
The Bash checker does not work on Windows. Run it from the repository root on a supported platform:
bash .agents/skills/check-release-deployments/scripts/check_release_deployments.sh <tag>
The checker converts the tag independently for Cargo, Python, and Node.js;
discovers the tracked package manifests in their respective source trees; and
reports every matching GitHub Actions release workflow, except Request NVSkills CI, before the package deployment table. For nightly alpha tags, it reports the
scheduled or manually dispatched nightly workflow run for the tag's commit and
UTC date instead of unrelated push runs at the same commit. If the Publish Rust crates, Python, or Publish TypeScript package workflow concludes with
failure, the corresponding Cargo, Python, or Node.js registry checks are
skipped and the table states why. For Python packages, it uses PyPI's JSON Index API at
/simple/<project>/ and verifies that the normalized version is in the
response's versions list. It waits at least 0.1 seconds before every request
to a registry website or GitHub API call to avoid rate limits. For Node.js
packages, it uses npm's registry API at
https://registry.npmjs.org/<package>/<version>. For Cargo packages, it uses
crates.io's versioned registry API at
https://crates.io/api/v1/crates/<crate>/<version> and excludes the internal
crates/fabric-python/Cargo.toml binding manifest.
Interpret the table status column as follows:
☑indicates the exact package version is deployed.○indicates the exact package version is not deployed.- Any other value is the HTTP status code returned by the registry.
The workflow is read-only. Do not retry failed or undeployed packages by publishing them unless the user separately asks to publish.
04 同仓库更多 Skills
default
Use this skill when asked to load the default test skill.
alternate
Use this skill when asked to load the alternate test skill.
swebench-debugging
Apply a focused reproduce-fix-test workflow to SWE-Bench repository tasks.
code-review
Review Python changes for correctness risks and missing test coverage.
validate-change
Choose and run the right NeMo Fabric validation matrix for a change instead of using one fixed test list
update-project-version
Update the NVIDIA NeMo Fabric release version across Cargo, Python, and TypeScript package metadata, internal Python dependency pins, integration metadata, and lockfiles. Use when bumping, synchronizing, or auditing NeMo Fabric package versions for a release.