Skip to content

1.0.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 02 Sep 07:37
· 45 commits to develop since this release
1.0.0
This tag was signed with the committer’s verified signature.
debop Sunghyouk Bae
SSH Key Fingerprint: j/MtFPs5VTMj1GDWlohDVzAFOGd8RcgfepE8tDGniMs
Verified
Learn about vigilant mode.
e701463
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

추가

  • LeaderBackendDiagnosticsProbe 공통 계약과 UNKNOWN 원인(CLIENT_STATE_UNCONFIRMED, PROVIDER_UNSUPPORTED, PROVIDER_EXCEPTION)을 built-in backend, Ktor, Spring, Micrometer 경로에 연결했습니다(Issue #766, PR #812, PR #813, PR #814, PR #816, PR #819, PR #820).
  • Prometheus dashboard 예제에 active connectivity probe, bounded reason metric/alert, HTTP scrape readiness 계약을 추가했습니다(PR #823, PR #836, PR #840).

변경

  • Kotlin 2.4, JDK 25, Gradle 9.7 기준의 1.0.0 개발선을 완료하고, 중앙 catalog ref를
    8efed120b91c4e1b1cfbfe1269321df325b08aef로 고정해 Projects/Exposed 안정
    버전을 사용하는 배포 경계를 확정했습니다(Issue #666, Issue #753, Issue #860, PR #838).
  • UNKNOWN reason, active probe, Micrometer counter, Spring health, Ktor route, Prometheus alert/runbook을 운영 해석이 가능한 bounded contract로 연결했습니다(PR #819, PR #820, PR #822, PR #823).
  • Spring lease-extension 관측 범위를 ObservationRegistry identity별 execution scope로 격리해 여러 application context의 telemetry가 섞이지 않도록 했습니다(PR #835).

버그 수정

  • Prometheus scrape 테스트가 첫 scheduled callback을 readiness 신호로 추정하지 않고 대상 job과 connectivity probe를 명시적으로 실행하도록 수정했습니다. 실패 시 HTTP status/body와 누락 metric 이름을 진단 메시지에 남깁니다(Issue #724, PR #840).
  • Redis strategic 후보 heartbeat 재등록이 결과 카운터와 lastCompletionTime을 되돌리지 않도록 하고, Redisson entry-lock 취소·late-acquisition·unlock cleanup과 Micrometer probe interrupt flag 보존을 같은 lifecycle 계약으로 닫았습니다(Issue #804, Issue #826, Issue #828, PR #830).

Contributors

Full Changelog: 0.5.0...1.0.0

Assets 2
Loading