My 2 key concerns with this approach are:

1. Can we actually share code in a straightforward way? If we use replace statements, do these correctly work for consumers? Last time I looked at it, it definitely doesn't work for a CLI, but may for a module import
   1. If we're not using replaces then we'll need to i.e. get Renovate to update the top-level dependency for all the child dependencies - it's what it's good at :) But slightly slows releasing
2. Releasing is also a little more complex (v1.13.0 introduces lots of transitive dependencies to client library #1142 and Migrate to multi-module project #1197 decided that a multi-module Go module wasn't worth it for the pain of releasing, at the time)
   1. This will mean Release Drafter will likely only work for the top-level module, and we'll need to hand-write the child modules

Otherwise, this sounds good! If we can make this work, this would probably be my preference, and would make it easier to keep things consistent

Other notes:

• If we're able to share most of the code, that'd be good
• What code doesn't make sense to share? Is there anything that's Router-specific that we do/don't want?
  • Or could we only provide a net/http middleware?
• We'd want to do the migration of the code to a single GitHub repo first, release that (so it's a drop-in replacement) then we'd
• Renovate right now can't auto-migrate folks for us (would be nice to get that in first, if possible: feat(gomod): add support for package replacements renovatebot/renovate#29575)