Bump traefik from v3.6.11 to v3.6.12 in /compose/production/traefik

[dependabot]

Bumps traefik from v3.6.11 to v3.6.12.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[claude]

PR Review: Traefik v3.6.11 to v3.6.12

This is a Dependabot patch-version bump with a single-line change in compose/production/traefik/Dockerfile.

Assessment: Safe to merge

What is being changed

• traefik:v3.6.11 updated to traefik:v3.6.12 in the production Traefik Dockerfile
• Patch-level bump (no breaking changes expected per semver)

Code quality

• The diff is minimal and correct. Only the version tag is updated; the acme.json setup and chmod logic remain intact.

Security

• Patch releases typically carry bug fixes and security patches, so upgrading is the right call.
• No new environment variables, volumes, or network configurations are introduced.
• Dependabot compatibility score badge indicates automated compatibility testing passed.

Performance

• Patch updates to Traefik rarely affect routing or proxy performance meaningfully.

Test coverage

• No application-level tests are relevant here; this is a pure infrastructure image bump.
• Recommend a smoke-test after deployment to confirm HTTPS termination and ACME certificate renewal still work correctly.

Verdict
No concerns. Routine maintenance update.