We are excited to announce an upcoming change that will simplify and streamline development across several of our key libraries. We’re consolidating three of our major repositories into a single monorepo.

What’s Changing?

We’re planning to migrate the following repositories:

• containers/common
• containers/storage
• containers/image

All three will be merged into a new monorepository:

• containers/container-libs

Migration Date

Planned migration date: August 26, 2025
We’ll share more updates as we get closer to the date.

What This Means for You

After the migration:

• All active development will move to the container-libs monorepo.
• The existing common, storage, and image repositories will remain accessible but read-only.
• These read-only repositories will no longer receive updates or new releases.

If your project depends on any of the current repositories, you’ll need to update your import paths to point to the new monorepo.

To ease this transition, we’ll be using Go vanity imports to provide stable import paths that won’t be affected by future structural changes. Stay tuned — we’ll send out an update once those import paths are ready.

If you’re curious about what the new monorepository layout will look like, you can explore a work-in-progress version in the https://github.com/containers/automation-tests/ repository.

Why a Monorepo?

Bringing these libraries together has several benefits:

• Easier development and testing of cross-cutting changes in a single PR.
• Simplified vendoring for consumers of these libraries.
• Faster and more coordinated release processes for Podman and related projects.

---

Stay tuned for more updates as we approach the migration date, and thank you for your continued support of the containers ecosystem!