Supported image versions and tags in Testcontainers modules

[HofmeisterAn]

Hi everyone 👋,

I'd like to open a discussion about how we handle supporting different image versions and tags in our Testcontainers .NET modules. This has been an ongoing challenge that we haven't formally addressed, and I'd love to hear the community's thoughts.

Right now, it's not clear which image versions or tags a module officially supports. Developers often assume any version will "just work", but that's not always the case. For maintainers, this makes it harder to triage issues and increases complexity. Supporting multiple versions leads to bloated configurations, and removing outdated APIs becomes nearly impossible due to backward compatibility.

My proposal is simple: We (community maintainers) officially support the latest major version and (any) LTS version(s). Anything beyond that is best effort, but developers shouldn't expect full support OOB.

Additionally, for breaking image changes, we could move module implementations to a new namespace or rename the classes. This would help keep things clean and make it clear which implementation supports which version, without overcomplicating the existing modules.

And, of course, developers can always fall back to the generic container builder for specific or custom configurations.

What do you think? How should we handle this long-term? Would clearer boundaries and communication help? Any other ideas?