Shipped · DevOps and infrastructure

What traefik/traefik shipped

The public repository of Traefik · github.com/traefik/traefik

Written by FoxPlug from the repository's own releases; not affiliated with Traefik. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/traefik/traefik; Traefik did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for traefik, free

Week of November 2, 2026

What shipped

Why it matters

This week brings two patch releases that carry a CVE advisory fix, so users on the v3.7 and v2.11 lines should upgrade. On the HTTP side, gRPC bidirectional streams get a regression test and path handling, Host matcher validation and Compress memory use are tightened, which affects routing and resource behavior for existing configurations.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Two patch releases this week: v3.7.17 and v2.11.61, both with a CVE advisory fix. Also in: a gRPC bidirectional stream regression test, stricter HTTP Host matcher validation, path parameter handling for dot-segments, and lower zstd memory in the Compress middleware.

Post for LinkedIn

Two patch releases landed this week: v3.7.17 and v2.11.61, each fixing advisory GHSA-xv5x-242w-7hf7 along with dependency updates. For HTTP routing, Host matcher values that are not valid hostnames or IP addresses are now rejected, matching HostSNI validation. Path sanitization removes parameters from dot-segments and empty segments, so /foo/..;bar/baz forwards as /baz. The Compress middleware now uses gzhttp's zstd encoder options to limit memory per response, and BasicAuth rejects passwords over 1024 bytes. A regression test covers gRPC bidirectional streams that could hang when a backend ends the stream while the client is still sending.

Week of October 26, 2026

What shipped

Why it matters

This week brought a release candidate for version 3.8 plus maintenance releases on the 3.7 and 2.11 lines, so users can try the new features early. It also extended Gateway API support with request mirroring, retries, backend client certificates and ClusterTrustBundle references, and closed connection leaks for NTLM and Kerberos authentication.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V3.8.0-rc.1, v3.7.17 and v2.11.61 are out. New this week: HTTPRoute RequestMirror and retry support, Gateway backend client certificates, ClusterTrustBundle CA references, and fixes for NTLM and Kerberos connection leaks.

Post for LinkedIn

Three releases this week: v3.8.0-rc.1, v3.7.17 and v2.11.61. The release candidate adds per-router responding timeouts, an acme reusePrivateKey option and managedFields stripping in Kubernetes informers. Gateway API support grew with the HTTPRoute RequestMirror filter, HTTPRoute retries, Gateway backend client certificates and ClusterTrustBundle CA certificate references. We also fixed backend connection leaks for NTLM and Kerberos authentication, avoided generated name collisions across namespaces in the ingress-nginx provider, and updated the Docker Basic guide to use v3.7. See the migration guide before upgrading.

Week of October 19, 2026

What shipped

Why it matters

This week brought two patch releases fixing a security advisory, so users on v3.7 and v2.11 have fixes available. It also landed several Gateway API additions, including backendRequest timeouts, frontend mTLS validation and a GatewayClass selector, plus a fix for flush, hijack and deadlines through wrapped response writers.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V3.7.16 and v2.11.60 are out with a security advisory fix and NTLM/Kerberos support in ForwardAuth. Also new: a per-router roundTrip timeout, Gateway API frontend mTLS, HTTPRoute backendRequest timeouts, a gatewayClass option, and a fix for flush, hijack and deadlines in wrapped

Post for LinkedIn

Two patch releases this week: v3.7.16 and v2.11.60 fix advisory GHSA-hrpp-p4fc-wwf8 and add NTLM and Kerberos support in ForwardAuth, also available in ingress-nginx auth-url on v3.7. On the Gateway API side, there is now support for the HTTPRoute backendRequest timeout, client certificate validation on Gateway.Spec.TLS.Frontend, and a gatewayClass option to watch a GatewayClass by name, with labelSelector deprecated in its favor. A new per-router respondingTimeouts.roundTrip option bounds the whole client transaction, and a fix makes http.ResponseController flush, hijack and deadlines work through the middleware chain.

Week of October 12, 2026

What shipped

Why it matters

This week brings security fixes to both the v3.7 and v2.11 lines, and the server no longer accepts CONNECT requests on any HTTP version. Several Kubernetes Ingress fixes change how auth-tls-secret and cross-namespace checks behave, so users of that provider should review the release notes before upgrading. A new tap middleware and changes to child router observability metadata give users more ways to inspect traffic and configure routers.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V3.7.15 and v2.11.59 are out, fixing three security advisories and rejecting CONNECT requests on every HTTP version. Also this week: a new tap middleware, auth-tls-secret fixes in the Kubernetes Ingress provider, and HTTPRoute backends defaulting to http when appProtocol is unset

Post for LinkedIn

Traefik v3.7.15 and v2.11.59 are released. Both fix three security advisories and reject all CONNECT requests, whatever the HTTP version, because CONNECT over HTTP/2 was not handled properly. The v2.11.59 release also bumps golang.org/x/net to v0.60.0. Beyond the releases, the Kubernetes Ingress provider gets fixes to the auth-tls-secret annotation: the cross-namespace check now runs for every Ingress, and client authentication applies to the whole host. HTTPRoute backends now default to http when appProtocol is unset. A new tap middleware sends a copy of requests and responses to Traefik services as JSON records, and non-root routers can carry observability metadata.

Week of October 5, 2026

What shipped

Why it matters

This week brings two new releases, v3.7.14 and v2.11.58, so users on those lines can update. Branch merges keep master and v3.7 current, and the Gateway API conformance reports were regenerated against master. A test comment typo fix makes the SPIFFE mTLS tests easier to read.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Release v3.7.14 (langres) and v2.11.58 (mimolette) are prepared. Merged v3.7 into master, merged v2.11 into v3.7, and regenerated Gateway API conformance reports. Also fixed a certificate typo in SPIFFE test comments.

Post for LinkedIn

This week Traefik prepared two releases: v3.7.14 (langres) and v2.11.58 (mimolette). The v3.7 branch was merged into master, with Gateway API conformance reports regenerated against master, and the v2.11 branch was merged into v3.7. A one-word spelling mistake in SPIFFE mTLS test comments was corrected from ceritificate to certificate. Users on the v3.7 and v2.11 lines can update to the new releases.

Week of September 28, 2026

What shipped

Why it matters

This week brings improved Gateway API support for complex Kubernetes deployments, better observability with OTLP metrics control, and expanded Ingress NGINX annotation compatibility. These changes address enterprise deployment patterns and strengthen security practices.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Traefik ships Gateway API ListenerSet support, fixes OTLP histogram aggregation, and expands Ingress NGINX annotation coverage for better Kubernetes integration.

Post for LinkedIn

This week's Traefik updates focus on Kubernetes improvements and observability. Gateway API ListenerSet support enables multi-tenant isolation, OTLP metrics now respect exporter configuration, and new Ingress NGINX annotations handle rate limiting allowlists and app-root paths correctly. These changes improve both enterprise deployments and cloud-native integrations.

Week of September 21, 2026

What shipped

Why it matters

This week focused on Gateway API correctness and cross-namespace routing, fixing collisions and shadowing issues that affected multi-listener deployments. Performance improvements to UDP handling and the P2C load balancer reduce resource waste, while the QUERY method support expands HTTP compatibility.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Fixed TLSRoute router collisions, Gateway API shadowing issues, and cross-namespace BackendTLSPolicy handling. Improved UDP buffer efficiency and added QUERY HTTP method support.

Post for LinkedIn

This week's releases focused on Gateway API stability and performance. We fixed router name collisions in TLSRoute deployments, resolved shadowing issues between different route types, and corrected BackendTLSPolicy ancestor reporting across namespaces. Performance improvements include optimized UDP datagram handling and P2C load balancer corrections. Added QUERY HTTP method support for expanded protocol compatibility.

Week of September 14, 2026

What shipped

Why it matters

This week's changes improve authentication handling for connection-bound schemes like NTLM and Kerberos, ensure consistent Ingress routing behavior, and fix a Kubernetes resource naming issue that could cause configuration collisions. These fixes strengthen reliability for users relying on advanced authentication and Kubernetes integration.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Improved NTLM and Kerberos connection isolation in FastProxy. Fixed SSL-passthrough routing consistency. Prevented Ingress-NGINX resource name collisions with dotted names.

Post for LinkedIn

This week we improved handling of connection-bound authentication schemes. FastProxy now properly isolates NTLM and Negotiate connections matching the default proxy. SSL-passthrough Ingress routes follow standard routing paths. We also fixed a Kubernetes resource naming issue in the Ingress-NGINX provider that could cause collisions when resource names contain dots.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-09.

Is this your repo? Ask us to remove this page.