Repository navigation
v3.0.0 — Feishu and Infoflow
Highlights
- Support Feishu alongside Infoflow: one enterprise application, independently managed resource groups, HTTP or WebSocket receiving, dedicated proxy configuration, native mentions and links.
- Add centrally managed application credentials, audited Secret viewing/rotation and safe deletion; clarify enterprise permissions and Agent-assisted deployment.
- Improve resource/queue administration, platform filters, Agent operation history, scoped service monitoring and compact broadcasts.
- Retain public task categories while restricting detailed notes to their owner and explicitly authorized super-administrator reads. Ordinary OP keys do not inherit detailed-note access.
Upgrade
Preserve the original data volume, encryption/JWT keys and metrics signing configuration. Use a single process; do not run duplicate receivers against the same application. Existing Infoflow bots, personal keys and Agent API routes remain supported. Feishu uses additive application/route/deduplication tables; this is not a rewrite of existing Infoflow credentials or a shared cross-platform resource pool.
Corporate application permissions/publication require administrator review before submission. Test-enterprise credentials must not be copied into production. Database readability alone does not guarantee a lossless downgrade of Feishu or privacy behavior.
Validation: reviewed integration passed 1,820 backend tests (7 skipped), 170 frontend tests, six required CI checks, affected API/browser checks and earlier real two-group/rendering acceptance. The release preparation PR also passed its own six required checks and both telemetry bundle builds.
Images and offline artifacts are built from tag v3.0.0; consult completed workflow results before deployment. Further credential migration, full audit lifecycle APIs and delegated detailed-note credentials are tracked separately in #57, #54 and #56.