Upcoming changes to wolfi-dev/os

[gaughen]

We’re rolling out changes starting next Wednesday, January 14, 2026 to dramatically improve Chainguard’s engineering velocity, change management efficiency, and, ultimately, package and image quality.

To support those efforts, we’ve consolidated several previously separate codebases (including Wolfi-related work) into a single Chainguard internal monorepo. This allows us to coordinate changes and test them together end-to-end.

What’s not changing:

• We will continue to maintain a fully open source mirror of wolfi-dev/os on GitHub.
• We will continue to welcome community contributions and package requests there.

What is changing:

• Contributions to wolfi-dev/os will be brought into our internal monorepo so we can run the full set of tests and validation before merging and releasing.

We realize this adds a hurdle to contributing, and may feel like a shift. We want to be transparent about why we’re doing it: higher quality, fewer regressions, and faster, safer delivery of improvements.

If you’d like to contribute, please follow the Contribution Guidelines as we’ll keep that current. We’ll do our best to shepherd changes through the process. If you are a Chainguard customer, please reach out to your Customer Success team for additional support.

Additionally, in preparation for this change, we will close existing issues and PRs filed in wolfi-dev/os on Monday, January 12, 2026 to reset and allow us to better manage external contributions going forward. If you feel your issue was closed in error, you can re-open or start fresh, following the Contribution Guidelines.

Keep being awesome,
Pat