• 1.6.0 ac682aaa54

    1.6.0
    All checks were successful
    continuous-integration/drone/push Build is passing
    continuous-integration/drone/tag Build is passing
    Stable

    drone released this 2026-11-19 12:47:31 +01:00 | 32 commits to main since this release

    The board decides join requests and Mila can email the applicant, staff see what changed in each release, members keep their own contact data, and sign-in and password reset are limited. Admins: read "Upgrade notes" before updating.

    Highlights

    • The board role can approve and reject join requests; Mila can email the applicant about the decision, with a paragraph of your own
    • "What's new" in the sidebar shows staff what changed and what they should check
    • Members change their own contact data and start on their own record after sign-in
    • The exit date is the last day of membership
    • Sign-in, password reset and join requests are limited per client and per address

    Upgrade notes

    Before the upgrade:

    1. Back up the database.
    2. Run SELECT lower(email), count(*) FROM members GROUP BY 1 HAVING count(*) > 1;. Each row is a group of members whose email addresses differ only in letter case; the upgrade stops on them. Change all but one address per group, or merge the members. If the upgrade did stop, the database is at 1.5.0: correct the addresses with 1.5.0, then upgrade again.
    3. Check your reverse proxy: the limits key on the last X-Forwarded-For entry from a trusted proxy (default: loopback and private networks). If the proxy reaches Mila from a public address, set TRUSTED_PROXIES; without a proxy, set it to none. See "Reverse proxy and client address" in the README.

    After the upgrade:

    1. Settings → "Emails to applicants": both emails start switched off on an existing installation. Check the preview and switch them on.
    2. The role "Vorstand" now decides join requests (permission set read_and_admit). To keep it read-only, set it back to read_only.
    3. Exit dates entered as the day after the last day (e.g. 01.01. instead of 31.12.) now keep the member one day longer; correct them if needed.

    Rolling back to 1.5.0: while 1.6.0 still runs, docker compose exec app bin/mv eval 'Mv.Release.rollback(Mv.Repo, 20261113175139)', then start 1.5.0.

    Join requests and emails to applicants

    • Approving or rejecting a join request can email the applicant, in the language of the request, with an optional paragraph of the club; new installations start with both emails on.
    • The join request page shows whether the email went out and can send it again.
    • New permission set read_and_admit: read access plus deciding join requests; new installations give it to the role "Vorstand".
    • Every email Mila sends shows the club's name at the top and "Sent with Mila" at the bottom.

    What's new

    • "What's new" in the sidebar lists the changes of the last releases for the person's role, with open tasks until marked as done. Accounts that exist before the upgrade start at 1.4.0, so 1.5.0 and 1.6.0 show as new once.

    Members and exit date

    • The exit date is the last day of membership: a member counts as active on that day and as former from the day after. The exit dialog and the member form say so.
    • Statistics count members with a future exit date as active, and members who join in the future not yet.

    Own data and account

    • Members edit only their contact data (name, email, address) on their own record; the rest is shown read-only. Roles on read_only and read_and_admit may do the same on their own record.
    • Members start on their own record after sign-in and see "My data", "My fees" and "Sign-in & security" in the sidebar.
    • The user menu entry "Profile" is now "Sign-in & security".
    • The password reset page confirms a request in plain words and links back to sign-in.

    Security

    • Members could change fields of their own record that only the board may change (e.g. exit date, notes, fee type); the server now accepts only their contact data.
    • Password reset: at most 3 mails per address and 10 requests per client per 15 minutes; the page answers the same whether the address exists or not.
    • Password sign-in is limited per client and address, per client and per address; the form says when to try again.
    • The join form's limit identified a client by X-Real-IP or the first X-Forwarded-For entry, from any sender, so a client could choose its own address and avoid the limit. It now uses the last X-Forwarded-For entry, and only from a trusted proxy.
    • Approving a join request accepted more fields than the dialog asks for; only the missing required values are taken now.

    Fixed

    • A link to a section scrolled its heading under the top bar.
    • The dot on "Join requests" in the sidebar was not announced to screen readers.
    • Approving a join request with Vereinfacht configured did not always sync the new member.
    • Members landed on an error page after signing in.
    • Creating a fee cycle reset the typed amount when the date changed.
    • Email addresses that differ only in letter case count as the same address (members, CSV import, join requests, linking accounts); addresses are still stored as entered.

    Dependencies

    • ash 3.37.3 → 3.37.4, spark 2.7.9 → 2.7.10, imprintor 0.9.0 → 0.9.1
    • PostgreSQL 18.7 in docker-compose.prod.yml
    Downloads