中文
本次 hotfix 主要解决 向 Session 添加消息时，隐私自动识别存在误判，导致部分普通内容被错误替换为隐私占位符，并产生无效隐私记录 的问题。
主要修复：暂时关闭 Session 隐私自动识别
暂时关闭新敏感值的自动识别与替换，避免继续误替换消息内容。例如，未登记的 password=example-password 现在会保持原样，不再自动创建 Session 隐私记录。此调整在代码中生效，无需修改配置。(#6680)
已登记隐私值的匹配与替换仍然保留，历史隐私占位符也继续支持读取还原。本次不会清理此前产生的隐私记录。
其他修复
English
This hotfix primarily addresses false positives in automatic Session privacy detection, which could replace ordinary message content with privacy placeholders and create invalid privacy records.
Main fix: temporarily disable automatic Session privacy discovery
Automatic discovery and replacement of new sensitive values are temporarily disabled to prevent further incorrect replacements when adding messages to a Session. For example, an unregistered password=example-password now remains unchanged and no longer creates a Session privacy entry. This change takes effect in code and requires no configuration changes. (#6680)
Matching and replacement of already registered privacy values remain active, and historical privacy placeholders can still be restored on reads. Previously created privacy records are not removed by this release.
Other fixes
- Raise the minimum SDK dependency to
0.1.17to provide the SDK APIs required by Compile. (#6596) - Fix MySQL task isolation across services and preserve legacy API compatibility. (#6676)
完整变更记录 / Full Changelog: v0.5.2 → v0.5.2.1