maintenance reboot!

[balint-backmaker]

maintenance reboot

Hey folks!
As you all know, this project has seen better days, as evidenced by:

• the numerous issues/pull-requests that do not have any answers or progress in a long time
• as well as not having any releases to pypi done in the entirety of 2023 😢

I know many people are using testcontainers in Python so we want to make it right for you!

To not beat around the bush, here is a short-list of what we'll fix ASAP, but each will be explained further below (or in detailed issues):

• Automate the release process via release-please - see feat(release): automate release via release-please #429
• Ease dependency management and packaging: move to pyproject.toml, possibly via poetry (already surfaced in Switch dependency management to poetry #204)

Follow-up changes:

• Re-instate the compose module with compose v2 - previous version was removed in a recent commit to main and is now defunct (breaking change, because the compose v1 python lib is defunct, too much risk otherwise!)
• Release 4.0.0 - there are too many changes to comb through manually if they are breaking or not and compose is definitely a breaking change

Tasks

Beta Give feedback

1. Switch dependency management to poetry #204
   👀 requires attention 🔧 maintenance +2
2. Migrate to DockerCompose V2 #358
   👀 requires attention 🔀 requires triage +2
3. feat(release): automate release via release-please #429
   +0
   

[alexanderankin]

@SergeyPirogov and @tillahoffmann can one of you add me as owner on https://pypi.org/project/testcontainers/ ? I'm https://pypi.org/user/daveankin/ (daveankin) on there - in service of figuring out automated releases.

update on this: Sergey has added me as owner on pypi, so while i don't quite have full write permissions here, there is the ability to publish new changes to pypi again.

since we don't have any pypi permissions on other testcontainer-* packages, (#412), we are waiting on #408 to actually publish again.

[alexanderankin]

creating this comment as a placeholder for a list of breaking changes in v4

• packages are all updated, no more ancient urllib/docker-py - windows version now uses named pipes as a result - Investigate what to do about "localnpipe" on windows #415
• elasticsearch class is renamed/aliased as per
• packages are all back in one package - all older aux packages are deprecated (The future of community modules (the testcontainers-* packages) #412)

[totallyzen]

for people who follow this one, please check out the new release process #429

It still needs a trusted publisher setup, but hoping to add that so we can prep a release soon 🚀

[totallyzen]

for keen eyes:

• I have removed Mark packages as typed #305 as proper completion of this is harder than expected, we need to prove the 4.0.0 release - not dropping the overall thing, just detaching from the "ready to release" criteria. More strong typing coming in with future 4.X releases
• I have removed "triage every issue" as it's more an ongoing task than a reboot marker

[totallyzen]

Hey folks! We now have a complete release process and compose is back in action.
I'm closing this issue and open two new issues to follow-up

• 4.x: quality of life, examples would be: typed packages, new modules, etc
• 5.x: API improvements, examples would be: introducing Ryuk (to be up to date with other TC implementations) and improve container guarantees