NVIDIA / NVIDIA/nvidia-container-toolkit

Release nvidia-container-toolkit v1.20.1

Open
#2,099 0 comments 0 reactions 1 assignee View on GitHub

@cdesiniotis is already working on this.

Since Sep 14, 2026.

release
Dominant language
Go
Stars
4.6k
Forks
592
Avg merge
1d 33m
Merged PRs (30d)
61

Description

Release Process

The NVIDIA Container Toolkit consists of the following artifacts:

  • The NVIDIA Container Toolkit container
  • Packages for debian-based systems
  • Packages for rpm-based systems

Release Process Checklist:

  • Create a release PR:
    • Run the ./hack/prepare-release.sh script to update the version in all the needed files. This also creates a release issue
    • Run the ./hack/generate-changelog.sh script to generate the a draft changelog and update CHANGELOG.md with the changes.
    • Create a PR from the created bump-release-{{ .VERSION }} branch.
  • Merge the release PR
  • Tag the release and push the tag to the internal mirror:
  • Wait for the image release to complete.
  • Push the tag to the the upstream GitHub repo.
  • Wait for the Release GitHub Action to complete
  • Publish the draft release created by the GitHub Action
  • Publish the packages to the gh-pages branch of the libnvidia-container repo
  • Create a KitPick
  • For non-experimental releases, schedule the package for publication to the CUDA Downloads repositories.

Troubleshooting

Note: This assumes that we have the release tag checked out locally.

  • If the Release GitHub Action fails:
    • Check the logs for the error first.
    • Create the helm packages locally by running:
      ./hack/prepare-artifacts.sh {{ .VERSION }}
      
    • Create the draft release by running:
      ./hack/create-release.sh {{ .VERSION }}
      

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.