Skip to content

cc-connect-next v0.3.0-beta.3

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 02 Sep 09:02
· 6 commits to main since this release
v0.3.0-beta.3
68f6aa3
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-beta.3

中文

这是 v0.3.0 的第三个 Beta，集中完成两条产品链路：更新现在可以明确选择 Stable 或
Beta，并在整条事务中保持同一通道；聊天 Feedback 则回到一次明确触发、一次直接
提交的短流程，同时保留结构化脱敏与无 Issue 链接的结果卡片。

Beta 渠道

  • 这个版本会作为 GitHub Prerelease 和 npm beta 发布，不会替换 GitHub Latest
    或 npm latest；稳定渠道继续保持 v0.2.1。

  • stable 仍是默认通道。明确参与 Beta 后，可以使用
    cc-connect-next update beta、cc-connect-next check-update beta、
    /upgrade beta，或配置 update_channel = "beta" 来持续发现 Beta-to-Beta
    更新；未选择 Beta 的现有用户行为不变。

  • 首次参与或切换到最新 Beta 可使用：

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

主要变化

  • 显式 Stable/Beta 更新通道。 CLI、聊天更新计划和 daemon 提醒都使用同一个
    通道值；发现结果、Release 类型、不可变 Plan 和最终文案会明确标识 Stable 或
    Beta，不再把 prerelease 写成 stable。Beta 复用同一套 checksum、staged 与
    installed version 探针、目标锁、备份和回滚边界。
  • 聊天 Feedback 一次触发直接提交。 明确执行 /feedback <描述> 或点击
    Feedback 动作后，会立即生成并提交有界、脱敏的结构化 Draft，不展示预览，也
    不要求第二次确认。Draft 只加入最近相邻、字段化、有界且脱敏的用户/Agent 诊断
    上下文，不上传任意 transcript、日志或配置。
  • 自动提示仍然零网络。 回合错误和能力缺口只准备一个一次性 Feedback offer；
    用户未点击时不会访问 Relay，一次点击则提交绑定当前 session/Draft 的精确内容。
  • 结果卡片保持极简。 飞书卡片提交后只显示“提交成功”或“提交失败”，不附
    Issue 链接、不另发结果消息。Agent 专用 CLI 仍保留独立的
    feedback preview / approval-token 协议。

兼容边界

  • 现有配置省略 update_channel 时继续使用 Stable；Beta 必须明确选择。发布本
    Prerelease 不会改变 Stable 用户的 GitHub Latest、npm latest 或默认更新结果。
  • 聊天 /feedback 是明确的外部网络动作，执行命令或点击按钮本身就是提交授权；
    自动错误/能力缺口提示本身始终不上传。
  • 精确更新原反馈卡片依赖飞书 card action callback 携带原始 message_id；文字
    路径只返回提交成功或提交失败，同样不输出 Issue 链接。
  • 发布 Beta 不会升级、覆盖或重启当前正在运行的 daemon，也不会部署 Relay；
    安装、正式配置变更和真实平台验证仍是独立操作。

English

This is the third v0.3.0 Beta. It completes two product paths: updates can now
select Stable or Beta explicitly and preserve that channel through the entire
transaction, while chat Feedback returns to one explicit trigger and one direct
submission without giving up structured redaction or the link-free result card.

Beta channel

  • This release is a GitHub Prerelease and npm beta. It does not replace
    GitHub Latest or npm latest; the stable channel remains v0.2.1.

  • stable remains the default. After opting into Beta, use
    cc-connect-next update beta, cc-connect-next check-update beta,
    /upgrade beta, or update_channel = "beta" to keep discovering
    Beta-to-Beta updates. Existing users who do not select Beta are unchanged.

  • Install or move to the latest Beta explicitly with:

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

Highlights

  • Explicit Stable/Beta update channels. The CLI, chat update Plans, and
    daemon notices share one channel value. Discovery, release type, immutable
    Plan, and terminal copy all identify Stable or Beta instead of calling a
    prerelease stable. Beta reuses the same checksum, staged/installed version
    probes, target lock, backup, and rollback boundaries.
  • One-action chat Feedback. An explicit /feedback <description> command
    or Feedback card action immediately builds and submits the bounded, redacted
    structured Draft with no preview or second confirmation. The Draft adds only
    recent adjacent, typed, bounded, redacted user/Agent diagnostic context—never
    an arbitrary transcript, log, or configuration map.
  • Automatic offers remain zero-network. Turn failures and capability gaps
    prepare a one-time Feedback offer without contacting Relay. One user click
    submits the exact Draft bound to that session; no click means no request.
  • Minimal terminal cards stay intact. Feishu shows only 提交成功 or
    提交失败, sends no separate result message, and never exposes the Issue URL.
    The Agent-only CLI keeps its separate feedback preview and approval-token
    protocol.

Compatibility boundaries

  • Omitting update_channel continues to select Stable; Beta is always an
    explicit opt-in. This prerelease does not change GitHub Latest, npm latest,
    or the default update result for Stable users.
  • Chat /feedback is an explicit external network action: the command or card
    click is the submission approval. Automatic error/capability-gap offers never
    upload by themselves.
  • Replacing the exact clicked Feedback card depends on the Feishu card-action
    callback carrying the original message_id. Text Feedback returns only
    success or failure and also omits the Issue URL.
  • Publishing this Beta does not install, replace, or restart a running daemon,
    and it does not deploy Relay. Installation, formal configuration changes,
    and real-platform validation remain separate operations.
Assets 9
Loading