release notes: follow-ups from #295 (Communique token limit)

未关闭
#296 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript, yaml
领域
release, tooling

调研方向

Start by reviewing the follow-ups from #295 and the Communique pin in mise.toml. The issue names src/tools/release-please-runner.ts, communique.toml, docs/RELEASE-PROCESS.md, src/tools/README.md, and release-please.yml; check the next pin bump or Release Please run for the stated trigger. Done means resolving the applicable follow-ups and checking runtime against the 20-minute timeout and the salvage warning.

由索引模型根据 Issue 内容生成。

描述

#295 raised Communique's response limit to max_tokens = 16384, so release notes are no longer cut off for releases with more than about 15 commits. Its review left these follow-ups:

  1. Log the model response's stop_reason. Today a cut-off answer is only inferred from the "malformed 3 times ... salvaging" warning.
  2. When the communique pin in mise.toml changes, update the "1.1.3 uses 4096" wording in MALFORMED_SUBMISSION_HINT (src/tools/release-please-runner.ts), the communique.toml comment, docs/RELEASE-PROCESS.md and src/tools/README.md.
  3. Decide whether to bump communique to 1.2.2 for its changed salvage behavior.
  4. On the next large release-please runs, watch run time against the 20-minute job timeout (release-please.yml) and the "salvaging" warning.

Trigger: the next communique pin bump, or a Release Please run that warns or fails again.


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high

主要语言
TypeScript
星标
30
派生
4
平均合并
3 小时 19 分钟
30 天内合并 PR
107

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

coder/agent-tty 的其他 Issue

查看 coder/agent-tty 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。