LoginSign Up
← Back to all sparks
W

werf

INFRA · APIS
Velocity5.0

GitOps delivery tool for building and deploying to Kubernetes

werf.io ↗

Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.

kubernetes-deliverymulti-channel-releasesbuildahdockerfile-fidelityv3-migration
◆Current state
werf publishes into parallel channels simultaneously — v2.75.3 tagged beta, ea and stable landed the same minute as v2.75.4 for alpha, while the v3 line runs separately through 3.0.2, a 3.0.0 alpha and a 3.1.0 dev build. The 2.x entries are corrective: buildah pull retries and serialisation, a stapel service script made executable regardless of umask, host cleanup no longer wiping other werf versions' git cache. The v3 entries carry the actual features.
◆Where it's heading
The v3 work is about making builds predictable and inspectable: embedded kubeconform schemas, a per-project meta-repo safeguard with a migration path, additional patches files with the defaults disableable, and repo-built scratch images made readable by dive. Meanwhile v3 alphas are restoring flags that v3 had dropped, which suggests the major is being trimmed and then walked back based on review. Dockerfile fidelity — COPY --parents, COPY/ADD --exclude in staged builds — is a recurring thread across both lines.
◆Prediction
Expect the 2.75 line to keep taking build-backend fixes while v3 stabilises, with more v2 flags restored in v3 alphas as review findings land before the major reaches a stable channel.

◆Recent moves

  1. 5h ago

    v2.75.3 stops host cleanup wiping other versions' git cache

    Host cleanup was deleting the live git cache belonging to other installed werf versions — a real hazard on machines running more than one. Shipped straight to beta, ea and stable together, which is how this project moves settled fixes.

    View source ↗
  2. 5h ago

    v2.75.4 makes buildah base-image pulls retry and serialise

    Concurrent base image pulls are serialised and a missing cached image id triggers a retry rather than a failure — both aimed at flaky build hosts. Scratch images built from a repo also become readable by dive, and stapel service scripts run regardless of umask.

    View source ↗
  3. 19h ago

    v3.1.0 embeds kubeconform schemas and adds a meta-repo safeguard

    The dev channel carries the v3 line's substance: kubeconform schemas embedded rather than fetched, a per-project meta-repo safeguard with a migration path, additional patches files with defaults disableable, and an opt-out for values schema validation when service values would break values.schema.json.

    View source ↗
  4. 7d ago

    v3.0.2 fixes build-log progress ordering

    A single fix assigning per-image build-log progress indexes by real start order, cut by an automated release tool. Cosmetic unless you are reading concurrent build output.

    View source ↗
  5. 8d ago

    v3.0.0-alpha.2 restores dropped deploy flags and honors COPY --parents

    --no-create-namespace and --lookup-resources come back after being dropped, and staged Dockerfile builds start honoring COPY --parents and COPY/ADD --exclude. The restorations show v3's scope being negotiated against what v2 users depend on.

    View source ↗