Skip to content

cc-connect-next v0.3.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Sep 15:29
v0.3.0
9ce6f96
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

cc-connect-next v0.3.0

中文

v0.3.0 汇总五个 Beta 的反馈、更新与会话可靠性改进。相较 v0.2.1，重点是
更完整的反馈隐私保护、明确的 Stable/Beta 更新通道，以及飞书话题和卡片操作的
准确归属。候选代码与 v0.3.0-beta.5 一致。

主要变化

  • 反馈入口更直接。 明确发送 /feedback <描述> 或点击反馈按钮即可提交
    已脱敏内容，不再二次确认；自动错误或能力提示在用户点击前不发送网络请求。
    错误反馈绑定原发起者，群聊共享会话、多工作区和固定工作目录都保持正确归属。
    提交结果更新原卡片，不额外发送 Issue 链接。
  • 反馈隐私与服务端保护。 采用 Foundation v0.1.2，补齐引号配置、转义值、
    Cookie、URL 凭据和宿主标识脱敏，排除时间未知或来自未来的诊断上下文。
    Relay 拒绝无效 UTF-8 和认证重定向，GitHub 操作采用仓库限定的 App 身份。
  • 更新通道明确可选。 stable 为默认通道；update_channel = "beta"、
    cc-connect-next update beta 或 /upgrade beta 可明确选择 Beta。
    更新展示精确版本、通道和发布说明，确认只执行已展示的同一计划；错误通道
    不能应用其他待确认计划。
  • 更新恢复与提醒更可靠。 更新保留校验和、安装前后版本探针、锁、备份与
    回滚保护。Unix Beta 保留恢复备份和执行权限，Windows 增加跨进程锁及防覆盖
    备份。主动提醒只发给明确列出的管理员私聊，部分失败会重试完整收件人名单。
  • Agent 可以安全反馈和重启。 本地 Agent 的 feedback preview 与
    feedback submit 使用同一脱敏和鉴权链；Agent 回合内请求重启会等待回答、
    卡片与已接收队列完成，再执行既有重启流程。
  • 飞书会话和卡片归属更准确。 真实私聊话题独立保存会话上下文与回复目标；
    同一 App 的多项目卡片绑定所属项目、收件人和操作者，慢速翻页刷新也保留绑定。
  • 配置和文本兼容修复。 动态 option 子键不再被误报为未知配置，非字符串
    option 值会明确报错；slash command 保持可复制，模型容量不足显示安全的重试
    或切换模型提示。

从 v0.2.1 升级

正式发布后可使用：

npm install -g cc-connect-next@latest
cc-connect-next --version

独立安装可使用 cc-connect-next update stable，聊天可使用 /upgrade stable。
省略 update_channel 仍使用 Stable；已显式配置 Beta 的用户需改为 stable，
才能持续跟随稳定通道。

  • 启用飞书 thread_isolation 的真实私聊话题会使用独立 session key，此前共享
    在普通私聊会话里的上下文不会自动迁移。
  • 主动更新提醒需要项目中明确列出的 admin_from 用户，以及唯一支持私聊投递的
    平台。空值或 * 无法枚举提醒收件人。
  • Agent/Platform 动态 option、环境变量与 peer alias 的值需为字符串；原先被
    静默忽略的数值等非字符串值现在会被拒绝。
  • 自定义反馈地址须为 HTTPS，路径精确为 /v1/feedback；仅 loopback 开发地址
    允许 HTTP。自托管 Relay 需独立更新部署，客户端升级不会自动更新服务端。
  • Agent Feedback 和回合内安全重启需要对应新版 daemon API；仅更换 CLI 不会
    自动更新仍在运行的旧 daemon。原生 Windows 运行尚未验证。

English

v0.3.0 brings together five Betas of feedback, update, and session reliability
improvements. Compared with v0.2.1, it adds stronger feedback privacy, explicit
Stable/Beta channels, and precise ownership of Feishu topics and card actions.
The candidate has the same runtime code as v0.3.0-beta.5.

Highlights

  • Direct chat feedback. /feedback <description> and explicit feedback
    buttons submit redacted content without a second confirmation. Automatic
    error or capability offers make no request before a user acts. Error offers
    belong to the initiating user, including shared sessions and multiple or
    fixed workspaces. Results replace the original card without an extra Issue
    link message.
  • Stronger privacy and Relay protection. Foundation v0.1.2 covers quoted
    configuration, escaped values, cookies, URL credentials, and host identifiers.
    Diagnostic context with unknown or future timestamps is excluded. The Relay
    rejects invalid UTF-8 and authentication redirects and uses a repository-scoped
    GitHub App identity.
  • Explicit update channels. Stable remains the default. Select Beta with
    update_channel = "beta", cc-connect-next update beta, or /upgrade beta.
    Updates show the exact version, channel, and release notes. Confirmation applies
    only the displayed plan and cannot substitute a plan from another channel.
  • Safer recovery and notices. Updates retain checksums, staged/installed
    version probes, locks, backups, and rollback. Unix Beta preserves recovery
    backups and executable permissions; Windows adds cross-process locking and
    backup protection. Notices go only to explicitly listed administrators in
    private chats, retrying the full list after partial delivery failure.
  • Safe Agent feedback and restart. Local-Agent feedback preview and
    feedback submit share redaction and authenticated approval. In-turn restart
    waits for the answer, cards, and accepted queue before the existing graceful
    restart lifecycle proceeds.
  • Precise Feishu ownership. Real private topics keep separate session
    context and reply targets. Cards shared across projects bind their project,
    recipient, and operator, including after asynchronous navigation refreshes.
  • Configuration and rendering fixes. Consumed dynamic option keys no longer
    appear unsupported, while non-string values fail explicitly. Slash commands
    stay copyable, and model-capacity failures offer safe retry/switch guidance.

Upgrade from v0.2.1

After publication:

npm install -g cc-connect-next@latest
cc-connect-next --version

Standalone installations can use cc-connect-next update stable; chat can use
/upgrade stable. Omitting update_channel still selects Stable. Users with an
explicit Beta configuration must change it to stable to follow that channel.

  • Real Feishu private topics with thread_isolation use distinct session keys.
    Context previously shared with ordinary private chat is not migrated.
  • Proactive notices require explicit project admin_from users and exactly one
    direct-message-capable platform. Empty or wildcard values cannot enumerate
    notice recipients.
  • Dynamic Agent/Platform options, environment variables, and peer aliases must
    contain string values. Previously ignored numeric or other non-string values
    are now rejected.
  • Custom feedback endpoints require HTTPS and the exact /v1/feedback path;
    HTTP is allowed only for loopback development. Self-hosted Relay operators
    must update and deploy separately; client upgrades do not deploy the server.
  • Agent Feedback and safe in-turn restart require the matching daemon API.
    Replacing the CLI alone does not update an already running daemon. Native
    Windows execution remains unverified.
Assets 9
Loading