Tags

Tags give the ability to mark specific points in history as being important
  • v0.2.16

    protected Release: v0.2.16
    lagport v0.2.16
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.2.15. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.2.15

    protected Release: v0.2.15
    lagport v0.2.15
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.2.14. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.2.14

    protected Release: v0.2.14
    lagport v0.2.14
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.2.13. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.2.13

    protected Release: v0.2.13
    lagport v0.2.13
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.2.12. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.2.12

    protected Release: v0.2.12
    lagport v0.2.12
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.2.11. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.2.11

    protected Release: v0.2.11
    lagport v0.2.11
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.2.10. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.2.10

    protected Release: v0.2.10
    lagport v0.2.10
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.2.9. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.2.9

    protected Release: v0.2.9
    lagport v0.2.9
    
    * A pending left entry survives a crash (a741b79)
    * A join interrupted after the member admitted it can be retried (d8ba63a)
    * A leave interrupted after its members were told says so at the next start (0ac8423)
    * Pending blob links survive a restart (b514819)
    * A corrupt copy no other node holds is moved into quarantine/ (65736b5)
    * A whole blob read from the node's own disk is checked as it streams (f548e2e)
    * lagport dump says how to get past a store a crash left unrepaired (0a127c6)
    * The background check reads a wrong hash twice before deleting (bbc0a44)
    * A leftover upload the start cannot delete no longer stops the node (4446bc8)
    * A commit finding its blob there syncs the directory too (e3f3342)
    
  • v0.2.8

    protected Release: v0.2.8
    lagport v0.2.8
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.2.7. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.2.7

    protected Release: v0.2.7
    lagport v0.2.7
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.2.6. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.2.6

    protected Release: v0.2.6
    lagport v0.2.6
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.2.5. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.2.5

    protected Release: v0.2.5
    lagport v0.2.5
    
    * The admin page shows a manifest's last pull as a date and its last write as a time (0e9a684)
    
  • v0.2.4

    protected Release: v0.2.4
    lagport v0.2.4
    
    * The healed join of the black-hole test runs under the normal join_wait (1deb113)
    * The coverage report leaves out any cargo registry path, wherever the registry lives (873972e)
    * devtools e43bf16: the warm coverage build and the test profile are the family's (8936610)
    * The gate keeps its coverage build and runs the tests on a lighter profile (5acce8c)
    * The UI goes to the repository list when the last manifest is deleted, and says "Loading" (4f7c5f1)
    
  • v0.2.3

    protected Release: v0.2.3
    lagport v0.2.3
    
    * The wrong-token test flips the token's bytes, not its characters (2d076f4)
    * A local admin token, `lagport admin` and `lagport dump` (738662b)
    * The admin UI shows every manifest, its time left, its copies and each repository's size (36ed548)
    * A new member is repaired at once, not at the hourly scan (af67d01)
    * devtools aaa20be: retry_verify's ten-minute budget and ci-lint's .vex_stale check (c80226e)
    * vex_stale reads every scanner the triage reads, Scout included (03b0e9b)
    * A verification is retried for ten minutes and says why it failed (ed999b3)
    
  • v0.2.2

    protected Release: v0.2.2
    lagport v0.2.2
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.2.1. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.2.1

    protected Release: v0.2.1
    lagport v0.2.1
    
    * The token test reuses the token before it waits for the keyring to spread (8cc88f0)
    * An idle member writes nothing to disk (931bf99)
    * The load-balancer test's relay waits longer than the delete it relays (22358f1)
    * The smoke test reads the process's uid from inside its pid namespace (122be64)
    * Bump devtools: the nightly assesses before it decides (73a5d46)
    * The scrub window takes a named time zone from an embedded database (aa52d99)
    * The background check reads in a window: --scrub-window (c683b5a)
    * The blobs may live apart from the metadata: --blob-dir (f1e89e5)
    * Two admin tests wait on liveness instead of reading it at one instant (bec34a3)
    * A peer's manifest test waits on b's state, not the writer's ack (e83f09d)
    * A forget's test asks again when c was heard after it was down (5162c43)
    * Bump devtools: the cooldown waives any advisory cargo audit fails on (7610cef)
    * pins.py retries a failed lookup; the long-link measurement leaves make test (ae3d104)
    * Multi-node tests reliable at one test per core; make test back to num-cpus (24dd2ec)
    
  • v0.2.0

    protected Release: v0.2.0
    lagport v0.2.0
    
    * make test: 4 tests at once by default; the long-link measurement alone (2140f28)
    * Bump devtools to reduce nightly emails (d9226f6)
    * An admission or a forget wakes an exchange round at once (af15aa4)
    * Node keys and a keyring replace the cluster CA; joins by token (d2fa7c8)
    
  • v0.1.3

    protected Release: v0.1.3
    lagport v0.1.3
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.1.2. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.1.2

    protected Release: v0.1.2
    lagport v0.1.2
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.1.1. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.
  • v0.1.1

    protected Release: v0.1.1
    lagport v0.1.1
    
    An automatic patch release: the nightly moved pins and the result differs
    from v0.1.0. Unsigned on purpose; devtools' tag-policy.sh admits it only as
    the next patch of a line whose .0 the release key signed.