• v1.0.0-Beta.16 3a6547ad01

    v1.0.0-Beta.16
    All checks were successful
    CI / check (push) Successful in 2m1s
    Release / release (push) Successful in 2m7s
    Docker Release / build-and-push (push) Successful in 4m11s
    CI / tests (push) Successful in 4m21s
    Pre-release

    k4wit0 released this 2026-09-02 17:51:38 +02:00 | 1 commits to main since this release

    Somewhere to set the space, and everyone moved to it

    Added

    • An administrator can change an account's space from its page. The endpoint
      for it shipped in Beta.14 without its control, so the limit could be set over
      the API and nowhere else — which is the same fault as code with no caller.

    Changed

    • The default space is a gigabyte, and accounts that already exist move with
      it. DefaultQuotaBytes is only consulted when an account has no quota row,
      and every account gets a row the first time anything is stored — so raising
      the number in Beta.14 applied to nobody who already existed, and every
      account went on reporting the 512 MB that was in force when its row appeared.
      Migration 019 moves rows still sitting on the old default; only those, and it
      is safe to assume they were never chosen because until now there was no
      control anywhere for choosing one.

    Fixed

    • The administration screen showed a ceiling of zero for an account that had
      stored nothing. It read the quota row directly, and an account gets that row
      the first time something is stored — so a fresh account was shown as
      unlimited while the person themselves was correctly told a gigabyte. Two
      screens of the same server disagreeing, and an administrator would have acted
      on the wrong one.
    Downloads