Hi! While there isn't a formal, published EOL policy for 1.x, the Testcontainers team has effectively moved focus to the 2.x line since the 2.0 release. Here's what we know:

1. No more feature development on 1.x — new features and improvements go into 2.x only
2. Critical security patches may still be backported to 1.x on a best-effort basis, but this isn't guaranteed
3. The migration guide is the recommended path forward

In practice, most open-source projects treat this as a soft EOL — 1.x will continue to work (it's already published to Maven Central), but you should plan to migrate to 2.x for ongoing support, bug fixes, and new container modules.

If your organisation needs a formal timeline, it might be worth opening a feature request to ask the maintainers to add an explicit EOL/deprecation notice to the docs.