What werf/werf shipped

Bundle commands now use Nelm for registry and archive work, publish and apply deploy like converge, and werf v2 refuses charts published by v3 instead of deploying them without their publish-time values and secrets. Failed Buildah builds no longer leak working containers.

This week's werf changes centre on bundles and build reliability. Bundle publish, apply, plan, render and copy now use Nelm for registry and archive handling, and werf's own bundle registry cache, archive format and ORAS v1 fork are removed. Publish and apply deploy exactly what converge deploys with the same flags: the chart is packed unchanged and values, secret values and set inputs are stored in a werf data directory instead of being merged into values.yaml. Bundle copy keeps all platforms of multi-platform images and writes standard OCI archives. Werf v2 now refuses to render, plan or deploy a chart published by werf v3 with a werf data directory, rather than deploying it without its publish-time values, secrets and annotations. On the build side, failed Dockerfile builds with the Bui

This week: v3.12.1 and v3.12.2 released. helm dependency update no longer panics without Chart.lock, values and set flags now override secret values, uninstall and dismiss no longer hang on elimination, Docker Hub login restored for build and export, cleanup keeps stages by custo

This week in werf: two patch releases, v3.12.1 (stable, rock-solid) and v3.12.2 (alpha, beta). Deploy uses saved plans containing a blind apply, and Dockerfile builds now work when a RUN mount option uses a base ENV and rebuild when a RUN bind-mount source changes. Helm users get fixes for dependency update panicking without Chart.lock and for uninstall or dismiss hanging on elimination. Values handling changed so --values and --set can override secret values, --set key=null can delete one, and export-values and import-values respect CLI values. Docker Hub login works again for build and export after werf cr login, and cleanup --keep-list accepts custom tags. Weekly channels were promoted.

Werf 3.12.0 and 3.12.1 are out: build can publish to multiple final repositories and publish cached images with require-built-images. Also fixed: Dockerfile binds rebuild on change, saved plans with a blind apply work, and --no-pod-logs is honored when executing plans.

Werf 3.12.0 and 3.12.1 are released. Build now publishes final images and custom tags to multiple final repositories in one invocation, and --require-built-images can publish already built images without running build instructions. Full-Dockerfile builds now rebuild when a RUN bind-mount source changes, and builds no longer abort when a RUN mount option references an ENV from the base image. Deploy fixes: saved plans containing a blind apply can be used with converge and bundle apply, --no-pod-logs is honored when executing plans, and --releases-history-max is respected with --use-plan. A lockgate bump removes a deadlock at the lock timeout boundary.

Two releases this week: v3.9.0 and v2.82.0, both exposing git source provenance to build commands and fixing unsuffixed list environment variables. Builds fetch only the pinned submodule commit, recover interrupted imports and skip broken cache stages.

This week werf shipped v3.9.0 and v2.82.0. Both expose git source provenance to build commands through WERF_GIT_SOURCES and accept unsuffixed list environment variables. Builds now shallow-clone only the pinned commit of a missing submodule, recover interrupted file imports in Stapel builds, report git preparation in operations statistics and skip cached stages with invalid image config sizes. Werf v2 also supports separate metadata repositories, and meta-repo migrate now reports progress with concurrent copying and a timeout.

Git LFS content is now included automatically in images. Builds verify downloaded contents against the selected commit. Also shipped: host cleanup removes root-owned temporary data, registry upload failures are reported, and submodule, worktree and kubectl fixes landed. Minor rel

This week werf builds include Git LFS object contents automatically in Stapel Git mappings and Dockerfile build contexts, using the selected commit's pointers and verifying downloaded contents so host LFS checkout settings cannot leave pointer files in images. Host cleanup can now remove selected project temporary directories whose container-created files are owned by root, and registry manifest uploads that end in EOF are reported as failures instead of being treated as successful. Commands like werf managed-images ls, werf cleanup and werf config render no longer fail after nested submodules were checked out from local objects, dev mode no longer removes user worktrees that are temporarily unreadable, and kubectl-related startup and plugin handling were fixed. Minor releases shipped acro

Werf updates: fixed --check-built-images flag, concurrent build synchronization, Dockerfile COPY stability, and chart-only command independence from Docker. Multiple reliability improvements in cleanup, git handling, and registry operations.

This week's werf updates restore critical build features and improve reliability across the board. The --check-built-images flag now works after being a no-op for months. Concurrent builds properly synchronize to prevent duplicate images. Dockerfile staging, git mappings, and cleanup operations all received fixes that prevent data loss and resource leaks. Chart-only commands no longer require Docker, and remote Docker contexts are now properly supported.

Werf v3.6.0: Build prep now 5x faster on large configs through concurrent anchor resolution and SSH connection reuse. v2 maintenance continues on branch 2.

Werf v3.6.0 shipped with substantial performance gains: build preparation dropped from 26 minutes to under 5 minutes on large configurations by processing content anchors concurrently and reusing SSH connections for git requests. Registry tag listings are now cached across stage lookups. The project also transitions to separate v2 and v3 maintenance branches, enabling continued v2 support while advancing v3 with improved Kubernetes namespace scanning and documentation.

Werf now preserves final images correctly in cleanup, speeds up GitLab registry operations, and fixes chart rendering for includes. Build reports include version info for better traceability.

This week's werf updates focus on cleanup reliability and registry performance. Final images are now properly retained in dual-repository setups, GitLab cleanup operations are faster with the manifest-by-tag API, and Helm chart rendering works correctly with includes at the project root. Build reports now include version information for improved traceability across CI runs.