• v0.1.4 6d534e8a42

    v0.1.4
    All checks were successful
    CI / cargo (push) Successful in 42s
    CI / docker (push) Successful in 21s
    Stable

    jlxq0 released this 2026-08-27 04:06:18 +00:00 | 27 commits to main since this release

    Corrects one sentence in this tag's annotation. The tag itself is not re-cut:
    an image already points at the ref, and moving it would briefly make it
    ambiguous which image the tag names.

    The annotation says the bypass residual costs "a stolen bearer plus LAN
    access". It costs a stolen bearer plus code running inside the cluster.

    Measured 2026-08-27: from a machine on the house LAN, 203.24.209.5 and its v6
    address time out after 8 s on ports 80 and 443, while
    https://carddav.kampong.social/ answers 401 from that same machine as a
    control. From a pod inside the cluster, both gateway addresses answer 401.
    MetalLB is the reason: the fondue pool holding 203.24.209.5/32 is a
    BGPAdvertisement peered across sgp, lax and zrh, and the L2 pool is a
    different address on home-lan, so no BGP session carries the route to the
    wifi.

    Everything else in the annotation stands. The corrected wording, the manifest
    parentRef where the fact can actually be broken, and the reason a hop count
    of 2 would be worse than 1 if it ever were, are in src/config.rs and
    AGENTS.md as of PR 16.

    Verified on this release: pod carddav-mcp-5cf76bb494-7dg5g running
    sha256:dd915b10117a66eb0d6fad3fcae1b6f99ac6fb1d0d77c405e2d03542cc580858,
    reporting xff_entries=2 trusted_proxy_hops=2 client_ip_resolved=true on 7 of
    7 authenticated requests.

    Downloads