chore: release v4.4.0

This commit is contained in:
xmanrui 2026-09-01 12:33:36 +08:00
parent 840e5aa857
commit 13fc85cdce
5 changed files with 22 additions and 6 deletions

View file

@ -6,11 +6,26 @@ This file records the notable changes in each dsh-im release. Its format follows
## [Unreleased]
## [4.4.0] - 2026-09-01
### Added / 新增
- 九个 IM 渠道新增统一的机器人级“访问设置”:私聊与群聊可分别选择允许所有用户或仅白名单用户,并独立配置默认命令权限、命令权限例外及白名单用户权限。策略按 `botId` 原子保存,保存后对新入站消息立即生效;原 owner、扫码接入者等既有特权身份继续保留访问与完整命令权限,Telegram 与 WhatsApp 旧访问配置会自动迁移。
All nine IM channels now provide unified per-bot Access settings. Direct and group chats can independently allow everyone or only allowlisted users, with separate default command permissions, command-permission overrides, and per-user allowlist permissions. Policies are atomically stored by `botId` and apply to new inbound messages immediately; existing privileged identities such as owners and QR provisioners retain full access and command permissions, while legacy Telegram and WhatsApp access settings migrate automatically.
### Changed / 变更
- 机器人卡片的设置页改为可扩展的横向 Tab 布局,现有 Bot ID、投递目标管理与专属使用文档统一归入“投递设置”页签。
Bot-card settings now use an extensible horizontal tab layout, with the existing Bot ID, delivery-target management, and dedicated guide grouped under the Delivery settings tab.
### Fixed / 修复
- 飞书长连接现在会先按常见 `NO_PROXY` / `no_proxy` 语义排除 `open.feishu.cn` 与 `open.larksuite.com`,仅在未命中排除规则时使用代理环境变量,避免本地代理导致长连接持续失败重试。
Feishu long connections now honor standard `NO_PROXY` / `no_proxy` matching for `open.feishu.cn` and `open.larksuite.com` before using proxy environment variables, preventing local proxies from forcing the connection into a retry loop.
- 飞书话题群中的卡片操作确认、watch 完成通知、命令及子流程失败提示现在都会回复到对应卡片或触发消息所在话题;没有可用话题锚点的历史数据继续沿用原有投递方式。
Feishu card-action confirmations, watch completion notices, and command or sub-flow failures in topic groups now reply inside the topic containing the relevant card or triggering message; legacy entries without an anchor keep their previous delivery behavior.
## [4.3.0] - 2026-09-01
### Added / 新增
@ -534,7 +549,8 @@ This file records the notable changes in each dsh-im release. Its format follows
- 改进 npm 发布包结构,保留 CLI 入口并避免安装脚本拦截。
Improved npm package contents to preserve the CLI entry point and avoid install-script blocking.
[Unreleased]: https://github.com/xmanrui/dsh-im/compare/v4.3.0...HEAD
[Unreleased]: https://github.com/xmanrui/dsh-im/compare/v4.4.0...HEAD
[4.4.0]: https://github.com/xmanrui/dsh-im/compare/v4.3.0...v4.4.0
[4.3.0]: https://github.com/xmanrui/dsh-im/compare/v4.2.1...v4.3.0
[4.2.1]: https://github.com/xmanrui/dsh-im/compare/v4.2.0...v4.2.1
[4.2.0]: https://github.com/xmanrui/dsh-im/compare/v4.1.1...v4.2.0

View file

@ -571,7 +571,7 @@ var React23 = __toESM(require("react"), 1);
// package.json
var package_default = {
name: "@xmanrui/dsh-im",
version: "4.3.0",
version: "4.4.0",
description: "\u628A\u4E5D\u79CD IM \u673A\u5668\u4EBA\u548C\u516C\u7F51 AI Office \u63A5\u5165\u672C\u673A DeepSeek Harness\u3002 Connect nine IM channels and a public AI Office to a local DeepSeek Harness.",
keywords: [
"deepseek-harness",

File diff suppressed because one or more lines are too long

4
package-lock.json generated
View file

@ -1,12 +1,12 @@
{
"name": "@xmanrui/dsh-im",
"version": "4.3.0",
"version": "4.4.0",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "@xmanrui/dsh-im",
"version": "4.3.0",
"version": "4.4.0",
"license": "MIT",
"dependencies": {
"@tencent-connect/qqbot-connector": "1.2.0",

View file

@ -1,6 +1,6 @@
{
"name": "@xmanrui/dsh-im",
"version": "4.3.0",
"version": "4.4.0",
"description": "把九种 IM 机器人和公网 AI Office 接入本机 DeepSeek Harness。 Connect nine IM channels and a public AI Office to a local DeepSeek Harness.",
"keywords": [
"deepseek-harness",