TL;DR: Chainguard is adopting a YY.MM based tagging format for tritonserver and tritonserver-no-backend container images on Jan 14, 2026.
| Announcement date | Planned Change date |
| Dec 10, 2025 | Jan 14, 2026 |
This communication includes the following topics:
What is changing?
On January 14th, new versions of tritonserver and tritonserver-no-backend container images will be tagged using a YY.MM tagging format (e.g., 25.12 for December, 2025), instead of using the tritonserver version (e.g., 2.6.2).
In addition, we’ve updated the build automation for these images to ensure they include the same versions of tritonserver, CUDA, and Python used by upstream tritonserver images from NVIDIA. This minimizes the risk of any compatibility issues between these components.
Why is Chainguard making this change?
The YY.MM tagging format is already used by upstream tritonserver images from NVIDIA, as well as tritonserver images with a backend from Chainguard (e.g., tritonserver-pytorch-backend). This change ensures our tagging and versioning approaches are consistent across all tritonserver container images.
What do I need to do?
No action is required if you use the ‘latest’ tag. If you pin to a specific tag, you will need to start using the YY.MM tagging format for images built on or after Jan 14, 2026.
Need help or have questions?
We're here to help - visit our support portal at support.chainguard.dev.
- Chainguard Team
Comments
0 comments
Please sign in to leave a comment.