Skip to content

v2.0.0

Choose a tag to compare

@hiroshiyui hiroshiyui released this 25 Sep 03:04
· 196 commits to main since this release
6a47771

Phase 8, contributor health, as one major release: 8B, the repository files
a contributor looks for; 8C, local setup; 8A, what CI checks; and 8D,
performance. With it come a security audit's fixes and the move to
Erlang/OTP 29 and Elixir 1.20.

Why a major version: building Baudrate now needs Elixir 1.20 and OTP 29
(mix.exs requires ~> 1.20), and the ActivityPub collections page
differently (below).

For operators: no migrations. The first deploy of this release compiles
Erlang/OTP 29 on the server, which takes several minutes; later deploys skip
it. Nothing needs installing by hand.

For other servers: the ActivityPub outboxes, followers, following and
replies collections now link ?page=true and continue with max_id (replies:
min_id). The numbered ?page=N links are still answered.

Added

  • CONTRIBUTING.md: setting up (the dev container, or your own toolchain),
    running the tests and the browser suite, and the conventions a change
    follows.

  • SECURITY.md: vulnerabilities are reported privately by email to
    hiroshi@ghostsinthelab.org, optionally encrypted with the OpenPGP key in
    doc/security-contact.asc (fingerprint
    37A4 5B21 B45E A42E BE6C E74C 9F35 3471 AF05 D276), with the response
    to expect and what is in scope.

  • CODE_OF_CONDUCT.md (Contributor Covenant 2.1).

  • Issue forms for bugs and feature requests (the feature form asks how the
    idea fits ADR 0056, and security reports are pointed to SECURITY.md), and
    a pull request checklist.

  • A dev container (.devcontainer/): the image CI tests in, pinned by
    the same digest, with PostgreSQL 15 beside it. Build output stays in
    volumes, so the container and a host build never overwrite each other.
    verify-toolchain.sh fails when its digests drift from CI's, and the CI
    image workflow updates it with every image bump.

  • CI's Static checks job (8A): translations must be extracted from the
    code, Dialyzer must report nothing outside a reviewed baseline, the three
    NIF crates must pass clippy -D warnings and their own unit tests, and the
    Ansible playbooks must pass ansible-lint at its strictest profile. A
    Coverage job merges the four test partitions into one report,
    published as a CI artifact, with no threshold. The CI image gains clippy
    and ansible-lint.

  • Rust unit tests for the sanitizer (what federated and Markdown HTML may
    keep, and that image sources stay within what the media proxy rewrites),
    the link extractor that the limits on new accounts and the filters rely on,
    and the feed parser. Each NIF is now a one-line wrapper around a plain
    function the tests call.

  • A test that every locale's .po file holds exactly the messages of its
    template, which translation_coverage_test.exs could not see before: a
    message missing from a locale entirely rendered in English with no failure.

Changed

  • ActivityPub collections page by row id (8D): first is ?page=true,
    and next is ?page=true&max_id=<id>, so a page costs the same at any
    depth and never skips or repeats an item when the collection changes between
    two requests. The older ?page=N is still answered.
    • The replies collection is paged too (oldest first, min_id); it used
      to return every comment in one document.
    • A user's following collection is one query; it loaded every follow
      the account had and paged them in memory.
  • A page of Articles costs a fixed number of queries (8D):
    ObjectBuilder.article_objects/1 preloads, counts comments and likes and
    checks for edits for the whole page at once. A 20-item user outbox page
    went from 104 queries to 6, and an /ap/search page from 101 to 9.
  • Cropper.js loads only on the avatar editor (8D). It was 108 KB of every
    page's app.js; it is now /assets/js/cropper.js, which the avatar hook
    fetches when a crop is first needed.
  • The timeline, board, notification and conversation lists are keyed
    (:key), so loading older messages, a new arrival or a regrouped
    notification sends only what changed. LiveView streams were considered and
    not used: every one of these lists is bounded (decision P8-D6).
  • Server provisioning downloads rustup-init pinned by version and SHA-256,
    like the CI image, instead of piping https://sh.rustup.rs into a shell.
  • Dialyzer's first run reported 404 warnings. 344 were specs naming a
    schema's t/0 type that did not exist; the 28 schemas now define it.
  • The development and test database settings read PGUSER, PGPASSWORD,
    PGHOST and PGPORT (and PGDATABASE in development), with the old
    values as defaults.
  • Erlang/OTP 29 and Elixir 1.20 (29.1.1 and 1.20.4), from 28 and 1.19.
    Operators do nothing by hand: the deploy now installs the Erlang and
    Elixir the release pins when the server lacks them
    (compiling Erlang
    takes several minutes, once) and refuses to build on anything else, so
    production runs exactly what CI tested. Development, the CI images, the
    dev container and the Ansible pins are checked to be one version.
  • Elixir 1.20's type checker found 34 places where the code guarded against
    something that cannot happen: fallback clauses no caller can reach,
    nil checks inside a condition that already rules nil out, and unused
    requires. They were removed rather than silenced, so a value that later
    goes unhandled fails the build instead of falling into a silent default.
  • daisyUI 5.7.46 (from 5.7.37), bug fixes only (dependency drift report
    #18). In themes other than the Aqua pair, a pressed toggle (like, boost,
    bookmark, watch) and the current page's link in the header now carry the
    button's active background; the Aqua themes keep their transparent
    toolbar buttons.

Fixed

  • A member's ActivityPub outbox listed their oldest posts first, while
    claiming newest first. Its query paired distinct with an order_by, and
    Ecto's DISTINCT ON put the article id first in the order, replacing the
    requested one. The same defect CLAUDE.md records for comment search.
  • Specs that left out an error the function returns: verifying a recovery
    contact can refuse with :no_live_challenge, and the delivery queue's page
    carries per_page. A spec for object-origin validation was so narrow that
    a correct guard in the inbox looked impossible.
  • The feed parser removed only adjacent repeated categories, so a, b, a
    kept both as (the Elixir side removed them again, so no post showed a
    duplicate tag).
  • The invite pages handled an :account_too_new refusal that invite
    generation stopped returning in March; the dead branch and its message are
    gone.
  • Test setup no longer times out under load: about twenty async test files
    seeded the roles table, each waiting on the previous test's uncommitted
    insert. The roles are now seeded once, committed, before the suite.
  • Saving a cropped avatar did nothing when the cropper had not loaded.
    Cropper.js became a separate file in this release; if it failed to load,
    the dialog stayed open and Save silently did nothing. Save now keeps the
    centred square instead, as an avatar chosen without cropping does.
  • A very large ?page= answered 500 on every listing and on the
    ActivityPub collections' numbered pages: the offset overflowed
    PostgreSQL's bigint and could not be sent. Page numbers are capped at
    1,000,000, and a page past the end is empty. The personal timeline no
    longer reads every row the viewer can see to show an empty page past its
    end.

Removed

  • doc/door-apps-development.md, a design for WASM plug-ins that no code
    implemented; the idea is one line in the Backlog.

Security

  • Signing in said which accounts exist, by how long it took. A wrong
    password for a real account ran bcrypt twice and an unknown name once, so
    timing the answer enumerated accounts, including those that appear in no
    byline. Resetting a password with a recovery code leaked the same the other
    way round: an unknown name cost a bcrypt, a wrong code for a real account
    none. Every path now costs exactly one, and a test counts them.
  • A rejected new password spent a recovery code. Resetting a password
    consumed the code before checking the new password, so a member who typed
    one the policy refused lost one of the codes that are their only
    self-service way back in. The password is checked first, and the code and
    the new password are now written together or not at all. The reset page
    also shows the policy's errors in the reader's language, and the username
    is matched without regard to case, as at sign-in.
  • The runtime's own security fixes (dependency drift report #18). The
    new Erlang/OTP 29.1.1 and Elixir 1.20.4 (see Changed) include fixes for
    two flaws that reach an instance through the TLS connections it opens to
    other servers: CVE-2026-89422 (the client accepted an unsolicited TLS 1.3
    pre-shared key) and CVE-2026-65634 (a certificate with oversized OID
    components could exhaust resources). Elixir fixes CVE-2026-75758
    (unbounded recursion on an invalid charlist).
  • An avatar id is stored only in the shape the server generates, and
    deleting an avatar refuses any other value, since it removes a directory.
    The feed bots' favicon fetcher names its temporary file randomly.