Skip to content

v0.19.0

Choose a tag to compare

@jasonodoom jasonodoom released this 25 Aug 21:57
· 42 commits to main since this release
v0.19.0
1d96eb6

Added

  • VEGA_EXCLUDE leaves matching store paths unpublished, as comma-separated
    globs over the path NAME (the part after the hash, so a pattern survives a
    rebuild): VEGA_EXCLUDE='*.erofs'. VEGA_MAX_NAR_BYTES does the same by size,
    as a blunt guard against an accidental multi-gigabyte push. Both are exposed on
    the Action as exclude and max-nar-bytes.

    This is for output no other machine can use. A host-specific microVM disk image
    is one to two gigabytes, changes whenever its guest config does, and nobody
    else will ever substitute it; on the deployment that asked for this, such paths
    were 40 of 49 publish minutes. An excluded path is neither uploaded nor
    attested, so it contributes to no tier, and anything referencing it leaves a
    consumer a dangling reference to build themselves. That is right for a
    host-specific artifact and wrong for anything another machine might want.

    Every skip is logged, with a count, the total NAR bytes and each path: a silent
    exclusion is indistinguishable from a cache that quietly lost paths. A pattern
    that matches nothing warns, as does excluding one of the build's own outputs,
    which forfeits its provenance. A malformed VEGA_MAX_NAR_BYTES fails the run
    rather than quietly reverting to no ceiling.

  • The builder gives its store a free-space floor, so a build collects garbage
    instead of taking the host's disk to zero. The image shipped only a periodic
    GC, which runs between builds and therefore cannot help when one build cycle
    produces more garbage than the disk has headroom: on a shared host that ran to
    0 bytes free twice in a day, against roughly 49 GiB of collectable paths per
    cycle. Nix's own min-free/max-free collect during a build, and the
    entrypoint now writes both into the generated nix.conf and prints them at
    boot.

  • VEGA_MIN_FREE and VEGA_MAX_FREE tune the floor, accepting a byte count or a
    binary suffix (VEGA_MIN_FREE=25G). VEGA_MIN_FREE=0 disables it, and the
    boot line says so rather than leaving the operator to infer it. The defaults
    are a fraction of the store's filesystem (10% and 25%, floored at 1 GiB, capped
    at 25 GiB and 60 GiB), because a fixed size is wrong at both ends: 25 GiB on a
    20 GB runner would collect on every check, and 1 GiB on a large shared host is
    a rounding error against one build cycle.

  • Booting against a mounted /etc/nix/nix.conf that sets no min-free warns.
    That file belongs to the operator and the entrypoint does not edit it, so the
    floor is theirs to set; the failure mode is a full host rather than a failed
    build, and it is invisible until it happens.

Fixed

  • vega verify checks whether Vega has withdrawn a binding. It verified the
    signature, the signed tree head and log inclusion, and never asked, so a path
    whose shared signature had been revoked still reported a clean pass, which is
    the one answer a verifier must not give. The revocation list is fetched from
    the cache origin (it is global, not per-tenant) and authenticated with the
    user's pinned shared key, never one the same cache served. A revoked binding
    now fails by every route, including the tenant and signature-only ones and the
    MCP risk gate an agent acts on, whatever key signed the build, since "Vega withdrew this" is a different
    answer rather than weaker evidence. A status that cannot be established is
    reported as unknown and is not treated as clean, so a cache that withholds the
    list is distinguishable from one with nothing to hide. The list carries a
    signed timestamp and total, both checked, so a stale replay or a truncated
    answer is unknown rather than clean.