Plugin published with all requirements met, no catalog discovery after 3 days, no traefiker-bot issue

Traefik Traefik v3 (latest)
1

Hi all,

I published a small Traefik v3 middleware plugin three days ago and it
hasn't been picked up by the catalog yet. Following the
Plugin Development Guide
I added the traefik-plugin topic at 2026-06-05 10:31 UTC, and at
T+~70h the catalog API still returns 404 with no diagnostic feedback
(no issue filed on the repo by traefiker-bot, no visible bot/webhook
activity on the repo events stream). I've read the half-dozen prior
"plugin not appearing" threads and verified every published
requirement; none of them seem to match my situation.

Could a maintainer take a look and let me know what the catalog
crawler is seeing (or refusing to see)?

Repo: https://github.com/jeroentrappers/traefik-plugin-request-id
Tag: v0.1.0
Module path: github.com/jeroentrappers/traefik-plugin-request-id

What the plugin does: ~80 LOC stdlib-only Go (no third-party deps,
Yaegi-safe). Sets X-Request-Id on the request and response — first
non-empty value from a configurable sourceHeaders list wins (default
[X-Request-Id, CF-Ray]), otherwise a fresh UUIDv4 from crypto/rand.

Verified prerequisites (everything I can check externally):

  • Repo is public, not a fork, not a template, not archived, not a
    mirror, not empty.
  • Default branch is master; v0.1.0 tag points to the same commit as
    master HEAD (sha 7c222ea).
  • .traefik.yml is at the root of the tagged commit and parses as
    valid YAML. Required keys present: displayName, type: middleware,
    import: ``github.com/jeroentrappers/traefik-plugin-request-id,
    summary, testData.
  • go.mod's module line matches .traefik.yml's import line
    exactly.
  • Go package name matches the last segment of the module path with
    hyphens converted to underscores: traefik_plugin_request_id
    (per the Yaegi convention).
  • GitHub topics on the repo: middleware, request-id, traefik,
    traefik-plugin.
  • MIT LICENSE present.
  • go vet, gofmt -l, and go test -race are clean (8 unit tests
    pass under <1 second).
  • proxy.golang.org/github.com/jeroentrappers/traefik-plugin-request-id/@v/v0.1.0.info
    returns 200 (module is cached server-side).

Catalog status:

  • curl -sI https://plugins.traefik.io/api/plugins/github.com/jeroentrappers/traefik-plugin-request-id
    → HTTP/2 404
  • gh issue list --repo jeroentrappers/traefik-plugin-request-id --state all
    → none (no traefiker-bot rejection)
  • gh api repos/jeroentrappers/traefik-plugin-request-id/events
    → only the original CreateEvent from 2026-06-05 10:00 UTC, no bot
    activity since.

For reference, I compared the .traefik.yml key shape against two
known catalog-accepted plugins
(mdklapwijk/traefik-plugin-request-id, killer-djon/traefik-correlation)
and they have an identical key set. My testData uses camelCase
(matching my Go struct's JSON tags), which killer-djon/traefik-correlation
also uses, so I don't think that's the issue.

Happy to add an iconPath, change anything else, or open this up for
the catalog team to investigate. Is there a diagnostic channel I'm
missing, or is the right next step to keep waiting? Last comparable
forum thread I found had the user wait several days before a
maintainer manually triggered a re-poll.

Thanks!