Skip to content

docs(boundary): 알려진 층 누수를 7.0 일정이 아니라 다음 major 후보로 적는다 - #422

Merged
airmang merged 1 commit into
mainfrom
docs/layer-leak-no-major-date
Oct 6, 2026
Merged

airmang merged 1 commit into
mainfrom
docs/layer-leak-no-major-date

Conversation

@airmang

@airmang airmang commented Oct 6, 2026

Copy link
Copy Markdown
Owner

요약

층 누수 가드의 허용 목록(tests/data/layer_leak_allowlist.json), 가드 스크립트, docs/architecture/product-boundary.md가 알려진 누수마다 "7.0에서 옮긴다"고 적고 있었습니다. 다음 major의 시기와 범위는 아직 정하지 않았으므로, "다음 major에서 옮길 후보"로 고칩니다. 코드 동작은 바뀌지 않습니다.

관련 이슈

#385 후속

변경 종류

  • 버그 수정
  • 기능
  • 문서
  • 리팩터링

체크리스트

  • pytest 테스트가 통과합니다. (tests/test_layer_leak_guard.py 14 통과, scripts/layer_leak_guard.py ok)
  • CHANGELOG.md를 갱신했습니다(해당하는 경우). — 문서 문구만 바뀌어 해당 없음
  • 문서 갱신이 필요한지 확인했습니다.

🤖 Generated with Claude Code

…or, not a 7.0 schedule

The allowlist, guard and product-boundary doc said each known leak is scheduled
to move in 7.0. No major release has been decided, so they now say the leaks
are candidates to move in a later major release.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@airmang
airmang merged commit b701d82 into main Oct 6, 2026
13 checks passed
@airmang
airmang deleted the docs/layer-leak-no-major-date branch October 6, 2026 05:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant