chore(release): v1.0.1 — upstream pending merge 3건 reconcile#8
Merged
Conversation
…dc#67) When editing an existing interactive message fails with "Message is not modified" (content unchanged after button press), the old code caught all exceptions and fell through to send a new message, causing duplicates. Changes: - Handle BadRequest "Message is not modified" specifically: keep existing message and return early instead of creating a duplicate - On other edit failures, send the replacement message first, then delete the old one only after the new one succeeds — prevents stranding users without controls if the replacement send also fails Fixes six-ddc#66
Co-authored-by: Joshua Frank <josh@tesseractmobile.com>
Write's tool_result text is just a confirmation message (e.g. "File created successfully at: ..."), not the written content — so line count was always 1. Now computed from the original tool_use input.content, with correct handling of trailing newlines. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
upstream f5ddd7f가 _format_tool_result_text에 tool_input_data 인자를 추가하고 Write의 line count를 input.content에서 계산하도록 변경. fork에만 있는 테스트 스위트(0e3c31c)가 옛 동작 기준이라 깨졌음. - parametrize에 tool_input_data 컬럼 추가 - Write 케이스: text는 실제 result 문자열로, tool_input_data={"content": "..."}로 line count 검증 - 나머지 도구는 tool_input_data=None Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
CHANGELOG.md에 [1.0.1] 섹션 추가, pyproject.toml 1.0.0 → 1.0.1, README의 현재 버전 표기 갱신. 이번 릴리스의 실제 코드 변경은 직전 4 commit: - a4451a9 Fix interactive UI duplicate messages (upstream six-ddc#67) - 4d43da2 fix: stop renaming user-created Telegram topics (upstream six-ddc#73) - 08d9c93 fix: show correct Write line count (upstream f5ddd7f) - 5bc3a2c test: TestFormatToolResultText 시그니처 갱신 (f5ddd7f 영향) CHANGELOG의 v1.0.0 섹션에 있던 "Pending upstream merges" 표에는 ✅ v1.0.1 reconcile 완료 메모 추가. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
upstream `six-ddc/ccbot`에 머지됐지만 fork에는 reconcile 안 됐던 3건을 cherry-pick + 버전 v1.0.0 → v1.0.1.
Cherry-picked commits
Test 변경
`f5ddd7f`가 `_format_tool_result_text` 시그니처에 `tool_input_data` 인자를 추가해서 fork-only 테스트 (`tests/ccbot/test_transcript_parser.py::TestFormatToolResultText`) 1건이 깨졌음. 새 동작에 맞춰 parametrize 컬럼 추가 + Write 케이스 수정.
SemVer 분류
PATCH bump (v1.0.0 → v1.0.1). 모두 버그픽스, 호환성 깨는 변경 없음. `_format_tool_result_text` 시그니처에 추가된 `tool_input_data`는 기본값 `None`이라 기존 호출과 backward-compatible.
Test plan
🤖 Generated with Claude Code