The Zarf team announced the release of Zarf 1.0 on November 9, 2026, featuring the new v1beta1 package schema and stronger package signing workflows.
What changed in Zarf 1.0
The Zarf team announced the release of Zarf 1.0, focusing on security, stability, and project sustainability. The release includes stronger package signing and verification workflows, more predictable behavior, and a package format built for ongoing compatibility.
The largest addition in version 1.0 is the v1beta1 Zarf package schema. This redesign converts years of feedback into a more intuitive experience, introducing component publishing for imports and simplifying package definition templating.
Transitioning to values
Package creators will notice a transition from variables to values. Values provide a structured home for configuration with standard Go templating and nested data support.
Version 1.0 includes a migration guide and tooling to help users convert existing packages. Defense Unicorns built Zarf to address challenges in getting software into air-gapped and constrained environments.
What to do
- Use the migration guide and tooling included in version 1.0 to help convert existing packages.
Key facts and where they come from
- Zarf 1.0 introduces the v1beta1 Zarf package schema.
The largest addition in v1.0 is the v1beta1 Zarf package schema.
- Package creators transition from variables to values in version 1.0.
One of the biggest changes package creators will notice is the transition from variables to values.
- Defense Unicorns built Zarf to solve airgap software delivery problems.
That’s the problem Defense Unicorns built Zarf to solve.
- Version 1.0 includes stronger package signing and verification workflows.
stronger package signing and verification workflows
