minio/minio image is now in maintenance-only mode, is there any plan to replace in docker-compose?

Summary

The minio/minio:latest image used in deploy/selfhost/docker-compose.yml has entered a maintenance-only stage — meaning no new features will be developed, and only critical bug/security fixes may be applied going forward.

Current usage in docker-compose.yml

plane-minio:
  image: minio/minio:latest
  pull_policy: if_not_present
  restart: unless-stopped
  command: server /export --console-address ":9090"

Question / Confirmation requested

Is the team aware of this change in MinIO's lifecycle status? Do you have a plan or timeline to:

• Continue using minio/minio:latest as-is (acknowledging the maintenance-only stance)?
• Or migrate to an actively maintained S3-compatible alternative (e.g., SeaweedFS, Garage, or a pinned/stable MinIO release with a clear upgrade path)?

Since Plane self-hosted relies on this image for file storage, it would be good to have clarity on the long-term strategy so self-hosters can plan accordingly.

References

• MinIO maintenance-only announcement: https://github.com/minio/minio (maintenance stage notice)

Start by reviewing deploy/selfhost/docker-compose.yml and the MinIO lifecycle reference in the issue. Read the comment thread for the team's current response and evaluate the listed storage alternatives; this issue is done when a concrete decision and upgrade plan are documented.