diff --git a/docs/release-notes/v1.11.9-en.md b/docs/release-notes/v1.11.9-en.md
new file mode 100644
index 000000000..2f78bf16c
--- /dev/null
+++ b/docs/release-notes/v1.11.9-en.md
@@ -0,0 +1,26 @@
+# CPA Manager Plus v1.11.9
+
+> 3 commits · 17 files changed · +781 / -172
+
+> [中文 ->](https://github.com/seakee/CPA-Manager-Plus/blob/v1.11.9/docs/release-notes/v1.11.9-zh.md)
+
+## Overview
+
+This release improves usage-data reliability and adds stronger safeguards around destructive actions. Account-history rollups can catch up during concurrent writes, large Monitoring selections no longer exceed SQLite limits, and manual AI provider or authentication-file deletion now requires a target-specific second confirmation.
+
+## Highlights
+
+### Fixes
+
+- Make account-history rollups wait for the SQLite writer slot during concurrent usage ingestion, preventing stale WAL snapshots from leaving rollup progress permanently behind (`manager-server/sqlite`).
+- Process large authentication-index, provider, and account filters through a single JSON parameter so persisted Monitoring selections no longer exceed SQLite's variable limit (`manager-server/monitoring`).
+- Require a second confirmation showing the masked target, deletion scope, or affected file count before manually deleting AI providers or authentication files (`web/providers-auth-files`).
+
+## Upgrade Notes
+
+- This release has no schema, API, or configuration changes and requires no manual migration.
+- Manual AI provider and authentication-file deletion now requires two confirmations. OAuth mapping cleanup and inspection-initiated automatic deletion are unchanged.
+
+---
+
+**Full Changelog**: https://github.com/seakee/CPA-Manager-Plus/compare/v1.11.8...v1.11.9
diff --git a/docs/release-notes/v1.11.9-zh.md b/docs/release-notes/v1.11.9-zh.md
new file mode 100644
index 000000000..84631a78f
--- /dev/null
+++ b/docs/release-notes/v1.11.9-zh.md
@@ -0,0 +1,26 @@
+# CPA Manager Plus v1.11.9
+
+> 3 commits · 17 files changed · +781 / -172
+
+> [English ->](https://github.com/seakee/CPA-Manager-Plus/blob/v1.11.9/docs/release-notes/v1.11.9-en.md)
+
+## Overview
+
+本次发布提升用量数据处理的可靠性,并加强高风险删除操作的保护。账户历史汇总可在并发写入期间稳定追上进度,大规模监控筛选不再触发 SQLite 条件上限,AI Provider 与认证文件的手动删除则增加目标明确的第二次确认。
+
+## Highlights
+
+### Fixes
+
+- 账户历史汇总在用量事件并发写入时会等待 SQLite 写入槽位,避免 WAL 快照失效导致汇总进度长期滞后(`manager-server/sqlite`)。
+- 监控筛选通过单个 JSON 参数处理大量认证索引、Provider 和账户,避免大规模已保存筛选返回 SQLite 变量上限错误(`manager-server/monitoring`)。
+- AI Provider 与认证文件的手动删除需要针对掩码目标、删除范围或受影响文件数完成第二次确认,降低永久误删风险(`web/providers-auth-files`)。
+
+## Upgrade Notes
+
+- 本版本不包含数据库结构、API 或配置变更,无需手动迁移。
+- 面板中的 AI Provider 与认证文件手动删除现在需要两次确认;OAuth 映射清理和巡检触发的自动删除保持原流程。
+
+---
+
+**Full Changelog**: https://github.com/seakee/CPA-Manager-Plus/compare/v1.11.8...v1.11.9
diff --git a/docs/release-posts/v1.11.9-telegram.html b/docs/release-posts/v1.11.9-telegram.html
new file mode 100644
index 000000000..7de8d83d5
--- /dev/null
+++ b/docs/release-posts/v1.11.9-telegram.html
@@ -0,0 +1,11 @@
+🚀 7 月 27 日 v1.11.9
+
+✨ 更新内容
+
+• 账户历史汇总在用量写入并发发生时可正常追上进度,不再长期滞后。
+• 监控筛选大量账户或凭证时不再因 SQLite 条件上限返回错误。
+• AI Provider 与认证文件的手动删除现在需要针对目标完成两次确认,减少误删风险。
+
+⚠️ 注意事项
+
+• OAuth 映射清理和巡检触发的自动删除保持原流程,仅面板中的手动删除增加第二次确认。