Skip to content

AzureQL v2.3.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 09 Sep 07:58
· 17 commits to main since this release
v2.3.3
91ad22b

AzureQL v2.3.3 — What’s Changed / 更新内容

中文

通知设置

  • 新增“设置 → 通知设置”，可直接读取、编辑并测试青龙当前通知渠道。
  • 动态支持 Gotify、Ntfy、Telegram、Webhook、Bark、邮件、Server 酱、PushDeer、钉钉、企业微信、飞书、PushPlus、WxPusher 等青龙官方渠道及版本命名差异。
  • 令牌、密钥和密码默认遮罩，仅保留在当前页面内存中；进程重建或切换账户后重新从当前服务器读取，避免跨账户串用。
  • “发送测试通知并保存”增加防重复提交、必填校验和安全错误分类；修复加载进度环偏心、拉伸及越出按钮的问题。
  • 若通知服务位于 mTLS 反向代理后，测试请求仍由青龙后端发出，不会继承 App 的客户端证书；请确保青龙容器可直接访问该服务。

按日系统日志

  • 设置中的“任务日志”入口更新为“系统日志”，按服务器时区列出最近 7 天日志并按需加载。
  • 支持长日志窗口化显示、滚动到底部、下拉刷新、空日志状态和 1 MiB 截断提示。
  • 兼容不接受 limit 查询参数的青龙 2.20.x：HTTP 400 时自动使用旧格式重试，同时继续在客户端限制读取上限。
  • 任务详情实时日志、订阅日志、日志 Repository 能力和 MCP 日志工具均继续保留。

验证与工程质量

  • 真实通知渠道“发送测试通知并保存”已通过手动实机验收；进程重建和多账户切换后未出现通知配置串用。
  • 较长系统日志滚动到底部及下拉刷新通过；任务详情实时日志与 MCP 日志读取快速回归通过。
  • 新增通知 Repository、字段注册表、ViewModel、系统日志数据层/ViewModel 与 Compose UI 回归测试。
  • 本地全量 JVM 测试、Android Lint、三组 Compose 测试源码编译、Debug/Release APK 构建全部通过。
  • GitHub Actions 推送验证、正式签名构建和 APK 签名校验全部通过。

English

Notification settings

  • Added Settings → Notification settings to load, edit, test, and save the active QingLong notification provider.
  • Dynamically supports QingLong providers including Gotify, Ntfy, Telegram, Webhook, Bark, Email, ServerChan, PushDeer, DingTalk, WeCom, Lark, PushPlus, WxPusher, and version-specific naming variants.
  • Tokens, keys, and passwords are masked by default and kept only in the current screen’s memory. Configuration is reloaded from the active server after process recreation or account switching to prevent cross-account reuse.
  • Added required-field validation, duplicate-submit protection, and safe error classification to Send test notification and save. Fixed the loading spinner being off-center, stretched, or rendered outside the button.
  • Notification tests are sent by the QingLong backend. If the provider is behind an mTLS reverse proxy, the app’s client certificate is not forwarded; ensure the QingLong container can reach the provider directly.

Daily system logs

  • Replaced the Settings-level Task logs entry with System logs, listing the latest seven days in the server timezone and loading each day on demand.
  • Added windowed long-log rendering, bottom scrolling, pull-to-refresh, empty states, and a 1 MiB truncation indicator.
  • Added compatibility for QingLong 2.20.x servers that reject the limit query parameter: the client retries the legacy request after HTTP 400 while preserving its local read limit.
  • Task-detail live logs, subscription logs, repository APIs, and MCP log tools remain available.

Validation and engineering quality

  • A real notification provider passed Send test notification and save on device. Process recreation and multi-account switching showed no configuration leakage.
  • Long system-log bottom scrolling and pull-to-refresh passed on device; task live logs and MCP log reads passed regression checks.
  • Added regression coverage for the notification repository, provider registry, ViewModel, system-log data/ViewModel behavior, and Compose UI.
  • Full local JVM tests, Android Lint, three Compose test-source compilations, and Debug/Release APK builds all passed.
  • GitHub Actions push verification, signed release construction, and APK signature verification all passed.

Requires Android 12 (API 31) or later and QingLong v2.17 or later.

Full Changelog: v2.3.2...v2.3.3

Assets 3
Loading