agentleFS
NVIDIAKnown publisherNVIDIA/NeMo-Relay/.agents/skills/check-release-deployments/SKILL.md

check-release-deployments

Skill238 starsChanged 2 months agoApache-2.0View on GitHub

Verify whether a tagged NeMo Relay release reached GitHub Actions, tagged Go module source, crates.io, PyPI, and npm. Use for publication status of a specific tag; not for publishing packages or creating tags.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Check Release Deployments

Require the release tag as input. Do not infer it from the current checkout, Git history, or package metadata.

The checker requires Bash, curl, gh, jq, just, and uv. Authenticate gh for NVIDIA/NeMo-Relay and verify it with gh auth status. The checker does not run on Windows. From the repository root, run:

.agents/skills/check-release-deployments/scripts/check_release_deployments.sh <tag>

It validates Relay's raw-SemVer tag format, converts the version to PEP 440 for PyPI, and checks the published package sets documented in RELEASING.md. It also verifies that the source-first Go module is present at the tag and reports the release-related GitHub Actions jobs. Registry checks run only after their publication jobs are verified successful. If the tag or release jobs cannot be verified, package checks are skipped.

  • ☑ means the exact package version is deployed.
  • ○ means that exact package version is not deployed.
  • 000 means a lookup or response could not be verified.
  • Other numeric values are HTTP statuses returned by the registry.

The Go row checks the tagged go.mod source because Relay does not publish a separate Go package-manager artifact.

This is a read-only workflow. Do not retry an absent or failed deployment by publishing packages unless the user separately asks to publish.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.