Milestones
List view
Issues targeted for the release after 1.1.0
No due date•0/17 issues closedReduce the operational work required to install, configure, and keep a self-hosted Coop deployment current. Provide a coherent default deployment path, production-ready supporting services, safe external-integration defaults, and clear upgrade guidance without coupling this work to datastore consolidation.
Due by December 31, 2026•0/1 issues closedLet organizations test, order, move, and safely roll out policy automation instead of changing production rules blindly. Make policy behavior reproducible across environments and provide evidence about the expected impact before enforcement changes go live.
No due date•0/1 issues closedGive moderation leaders a structured way to measure and improve reviewer and automated-decision quality. Support secondary review, representative sampling, feedback, and decision context without creating a second moderation workflow.
Due by December 31, 2026•0/1 issues closedEnsure Coop produces complete, standards-aligned NCMEC reports and can support follow-up reports without losing prior-report relationships. Validate the full workflow continuously so required data or API compatibility cannot silently regress.
No due date•0/1 issues closedBring Coop's application, development, and container dependencies up to supported and secure versions without destabilizing adopters. Fix vulnerabilities, keeps each package's lockfile healthy, and prevents automated upgrade pull requests from accumulating indefinitely.
Due by December 31, 2026Make production failures diagnosable and ensure infrastructure problems are represented accurately to operators and API consumers. Memory growth is the immediate reliability gate. webhook delivery visibility and correct outage responses complete the initial scope.
No due date•0/1 issues closedAllow Coop to run entirely on Postgres without removing the existing Scylla, ClickHouse, or Redis paths needed by larger deployments. Each data domain should depend on a stable interface, with configuration selecting either its existing datastore implementation or a Postgres implementation. This helps adopters decide the shape of their deployments.
Due by December 31, 2026Turn Coop's existing HMA integration into a complete, organization configurable hash-bank workflow. Organizations should be able to manage bank content, write reviewed media to company verified destinations, capture source specific false positives, tune matching behavior, and operate the integration with clear health and permission boundaries.
Due by December 31, 2026•0/1 issues closedGive reviewers and supervisors one coherent set of tools for understanding workload, meeting SLAs, managing ownership, and handling work at scale. The epic is complete when teams can see pending work, measure claim and handle time, escalate or reassign safely, control queue access, and perform bulk operations.
Due by December 31, 2026•0/1 issues closedRemove the high-frequency friction adopters encounter in moderation, investigation, child-safety, and admin screens. This epic intentionally bundles small, visible improvements that make common work clearer and faster without changing the core architecture.
Due by December 31, 2026•0/1 issues closed- No due date•0/5 issues closed
The release coming after 1.0.2
Overdue by 2 day(s)•Due by September 18, 2026•41/44 issues closed