Traefik has published release v2.11.60, a new patch tag on the 2.11 maintenance line. The release is available from the official GitHub releases page under the v2.11.60 tag, and it targets teams still running the 2.x branch of the cloud-native reverse proxy and load balancer rather than the newer 3.x series.
The source material for this release is limited to the tag itself, so the concrete details are:
- Version
v2.11.60is a patch-level increment over the previousv2.11.xtags, published as a GitHub release undertraefik/traefik. - It lives on the 2.11 maintenance branch, which continues to receive patch updates alongside the actively developed 3.x line.
- The release tag is the canonical reference for the exact commit and associated build artifacts for this version.
- Anyone pinning container images or binaries should reference the fully qualified
v2.11.60tag to stay on a fixed, reproducible version.
Because the release notes as provided contain no changelog entries, treat the tag as the authoritative source: check the linked release page for the attached binary checksums, container image digests and any commit-level diff before upgrading a production environment. If you track Traefik through a package manager or an image reference such as a pinned v2.11 tag, bump it explicitly to v2.11.60 rather than relying on a floating minor tag.
Why it matters to developers: staying current within a maintained branch is the low-risk path to pick up routine fixes without adopting the breaking changes that can come with a major version jump. For operators running 2.11 in production, v2.11.60 is a straightforward drop-in replacement candidate, but verify the diff and test your routing configuration in staging first, especially if you depend on specific middleware or provider behaviour documented for the 2.11 line.
Source: https://github.com/traefik/traefik/releases/tag/v2.11.60