From dc760fc2d1cb949fe7f0d5f485d081705d4e2a1a Mon Sep 17 00:00:00 2001 From: donghyeon-ka Date: Tue, 29 Sep 2026 12:57:24 +0900 Subject: [PATCH] =?UTF-8?q?review-followup=20Wave=203=20=EB=9D=BC=EC=9A=B4?= =?UTF-8?q?=EB=93=9C=203(P27):=20=EB=B9=8C=EB=93=9C=20=EC=9E=94=EC=97=AC?= =?UTF-8?q?=20=E2=80=94=20INTERNAL=5FERROR=20=EB=B9=84=EC=9E=AC=EC=8B=9C?= =?UTF-8?q?=EB=8F=84,=20messaging=20=EC=B9=B4=EB=93=9C=20=EA=B2=80?= =?UTF-8?q?=EC=A6=9D=20leaf=20=ED=85=8C=EC=8A=A4=ED=8A=B8,=20cosign=20?= =?UTF-8?q?=EC=84=9C=EB=AA=85?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - 결정 28: `INTERNAL_ERROR` retryable=false(레지스트리·코드·문서·기대값) - 결정 29: messaging 카드 검증을 `adapter:outbound:messaging` 테스트로, snakeyaml은 test configuration에서만 - 결정 31: release.yml에 cosign keyless 이미지 서명·검증 job(공식 체크섬 고정 설치, id-token은 그 job만) - persistence-fileserver `ca.api-surface`(P16-new-6), `ca.release-provenance` 제거(BUILD-O3-5 일부) - 에이전트가 세션 재시작으로 중단 — 결과 파일은 오케스트레이터가 작성, 미커밋 `jvm-test-suite` 전환은 패치로 보관 - 통합: messaging CLAUDE.md 충돌(encoder 위치 + test 전용 snakeyaml 문장 병합) 검증: ./gradlew mainCheck, -p build-logic test, -p optional-platforms ci, releaseCheck -PgitRevision 통과. ci verifyDependencyLocks --warning-mode=fail은 web-advanced `WebStreamingSoakIT` 1건(1001 > 1000) 외 통과 — 단독 3회 통과, 경합 가능성으로 ORCH-new-3 행에 기록 Co-Authored-By: Claude Opus 5.5 (1M context) --- build.gradle | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/build.gradle b/build.gradle index e91af3c..59808a9 100644 --- a/build.gradle +++ b/build.gradle @@ -1,16 +1,10 @@ plugins { id 'ca.architecture' - // Without it every gRPC leaf's jar is versioned 0.0.1-SNAPSHOT, because JavaConventionsPlugin - // falls back to that when the root has no ReleaseProvenanceExtension — so one commit produced - // two artifact sets under two different version schemes, and only one of them could be traced - // back to a revision. - id 'ca.release-provenance' } -ext.sourceRevision = providers.gradleProperty('gitRevision') - .orElse(providers.environmentVariable('GIT_SHA')) - .orElse(providers.environmentVariable('GITHUB_SHA')) - .getOrElse('unknown') +// No `ca.release-provenance` any more: each gRPC leaf's `ca.java-conventions` derives its version +// and `sourceRevision` from the same -PreleaseVersion/-PgitRevision (GIT_SHA, GITHUB_SHA) inputs the +// main build reads, so one commit produces one version scheme in both builds (review BUILD-O3-5). tasks.register('resolveAndLockAll') { group = 'build setup'