Skip to content

v0.53.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 27 Jun 07:21
· 1174 commits to main since this release
v0.53.2
c85a9f0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Added

  • Manage all of a guild's initiatives from one place. Guild settings has a new Initiatives tab (admin only) listing every initiative with its member count, where you can archive, delete, or grant the Project Manager Full access for each one without opening each initiative individually.
  • Archive an initiative to hide it from the sidebar. Archiving keeps everything intact (projects, documents, tasks, queues) but removes the initiative from the main sidebar for everyone; unarchive any time to bring it back. Available from the new Initiatives tab and from an initiative's Danger zone settings. Archiving is guild-admin only.
  • Per-guild storage limit. A guild can now have a maximum total upload storage; uploads that would push the guild over its limit are rejected. Defaults to unlimited, so existing guilds are unaffected until a limit is set.
  • Set per-guild storage limits from the Admin dashboard. Platform admins and owners get a new Guilds tab under Settings → Admin that lists every guild with its member count and current cap, where you can set (in GB) or clear each guild's maximum upload storage. Lowering a cap below current usage blocks further uploads but never deletes existing files.
  • Optional S3-compatible object storage for uploads. Uploads can now be stored in an S3-compatible object store you point it at (a self-hosted Garage instance, AWS S3, R2, etc.) instead of the local filesystem, via STORAGE_BACKEND=s3 and the new S3_* settings. The filesystem remains the default, so existing deployments are unaffected. See docs/OBJECT_STORAGE.md.
  • Zero-downtime migration from local to S3 storage. A python -m app.db.backfill_uploads_to_s3 job copies existing local uploads into the bucket (idempotent, content-type preserved, integrity-verified), and a new S3_LOCAL_FALLBACK setting serves any not-yet-copied blob from local disk during the cutover — so flipping a deployment with existing uploads onto S3 never drops a file. See docs/OBJECT_STORAGE.md.

Fixed

  • Deleting a guild now also removes its uploaded files. Previously a deleted guild's stored blobs were left orphaned on disk (or in the object store); guild deletion now sweeps the guild's storage namespace. Local uploads are also organized into per-guild folders (uploads/guild_<id>/), with any existing files relocated automatically on startup — no action needed.

Downloads

Android App

No new app build this release — installed apps update automatically over the air on next launch.

Docker Image

docker pull morelitea/initiative:0.53.2

Or use latest tag. View on Docker Hub.

Assets 2
Loading