Retire the /passthrough/* 410 migration tombstone in the first release after 0.10.0 #1010

Activity

1. jarvis9443

   added

   release-debtDeferred compatibility work due at a specific future release — swept in aisix-release Phase 0Deferred compatibility work due at a specific future release — swept in aisix-release Phase 0

   on Aug 20, 2026
2. jarvis9443

   changed the title [-]Retire the /passthrough/* 410 migration tombstone at 0.11.0[/-] [+]Retire the /passthrough/* 410 migration tombstone in the first release after 0.10.0[/+] on Aug 20, 2026
3. coderabbitai commented on Aug 20, 2026

   

   coderabbitaiBot

   on Aug 20, 2026 – with coderabbitai

   Last edited by coderabbitai

   More actions

   🔗 Related PRs

   #853 - feat(config): request_body_limit_bytes defaults to 0 = no cap; uniform 413 surface [merged]
   #982 - feat(passthrough): explicit PassthroughRoute resources replace the implicit provider tunnel [merged]
   #984 - fix(passthrough): forward-proxy routes may claim reserved prefixes and mirror the whole path [merged]
   #986 - feat(passthrough): per-request envelope detection, drop protocol/streaming config [merged]
   #983 - fix(passthrough): OTLP route/identity attribution, route on rejected events, header_key 401 names its header [merged]

   ---

   📝 Issue Planner

   _{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

   • Create Plan

   ---

   🧪 Issue enrichment is currently in open beta.

   You can configure auto-planning by selecting labels in the issue_enrichment configuration.

   To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

   issue_enrichment:
     auto_enrich:
       enabled: false

   💬 Have feedback or questions? Drop into our discord!
4. jarvis9443

   added a commit that references this issue on Aug 20, 2026

   feat(compat): make time-boxed compat code come due mechanically (#1011)

   ...

   2f48ef9
5. jarvis9443 commented on Aug 20, 2026

   

   jarvis9443

   on Aug 20, 2026

   ContributorAuthor

   More actions

   This deadline is now enforced instead of remembered — #1011 put a marker on LEGACY_TUNNEL_GONE:

   COMPAT-SINCE: 0.10.0 #1010 — 0.10.0 removed the implicit `/passthrough/:provider/*rest`
   tunnel, and a migration pointer beats a bare 404 while un-migrated callers are still out
   there; the public docs promise the 410 for one release, then plain 404s.
   

   crates/aisix-core/tests/compat_debt.rs runs in the required rust unit + coverage job and fails every PR once a stable tag with a higher MAJOR.MINOR than 0.10.0 exists — 0.11.0 or 1.0.0, whichever it turns out to be. Release candidates don't count as shipped.

   What the gate does not decide is the judgement call in this issue: it forces the question at the deadline, it doesn't answer it. The WARN was added so we could size un-migrated traffic first, and the paired docs sentence still has to be updated by hand — neither is visible to the gate. It also fires only once the next release has already shipped; the aisix-release Phase 0 sweep is what catches this in the release it's due in.
6. jarvis9443

   closed this as completedin #1054on Aug 27, 2026