Is Traefik v3.7.17 safe to update?

Yes, with care. No explicit breaking changes, but the notes mention migrations, deprecations or a new release line. Back up first.

What users are reporting

1 public report(s) mention this version, none clearly describing breakage. Most-discussed: “v3.7.17: provider plugin panics at load in yaegi genInterfaceWrapper (Go 1.27, likely traefik/yaegi#1734)”. Sources: GitHub · checked 2026-11-02

• v3.7.17: provider plugin panics at load in yaegi genInterfaceWrapper (Go 1.27, likely traefik/yaegi#1734) (GitHub)

Reports are from public issue trackers and forums. Their count isn't a failure rate, and an empty list doesn't prove an update is safe.

⚠️ What breaks

Nothing explicitly breaking is flagged, but the notes mention migrations, deprecations or larger changes. Most setups upgrade fine. Back up first and update when you have time to check.

From the release notes

• Important:** Please read the [migration guide](https://doc.traefik.io/traefik/v3.7/migrate/v3/#v3717).

Read the full official release notes →

✅ What to do first

1. Read the official release notes (linked in “What breaks”).
2. Back up config and data (snapshot the VM/volume if you can).
3. Note the version you are on now, so you can roll back.
4. Update, then check logs and core functions before walking away.

↩️ How to roll back to v3.7.16

Docker: snapshot/back up the data volumes first, then if needed change the tag back, e.g. image: traefik:v3.7.16, and run docker compose up -d. Tag format varies by image (some drop the “v”), so check the registry’s tag list.