docs: sweep stale 0.6.0 references after 3.0.0 renumber

README.ko.md

@@ -72,7 +72,7 @@ ApiEventListener  (api-log-core)
 
 ## 설치
 
-v0.6.0부터 스타터가 4개 아티팩트로 분리됐습니다 — 백엔드 비종속 코어 1개 +
+v3.0.0부터 스타터가 4개 아티팩트로 분리됐습니다 — 백엔드 비종속 코어 1개 +
 영속화 백엔드 1개. **`api-log-core` 1개 + 백엔드 1개**를 직접 골라 추가:
 
 | 좌표 | 언제 쓰나 |
@@ -91,21 +91,21 @@ v0.6.0부터 스타터가 4개 아티팩트로 분리됐습니다 — 백엔드
 <dependency>
     <groupId>kr.devslab</groupId>
     <artifactId>api-log-jpa</artifactId>
-    <version>0.6.0</version>
+    <version>3.0.0</version>
 </dependency>
 
 <!-- 또는 리액티브 앱에서 R2DBC -->
 <dependency>
     <groupId>kr.devslab</groupId>
     <artifactId>api-log-r2dbc</artifactId>
-    <version>0.6.0</version>
+    <version>3.0.0</version>
 </dependency>
 
 <!-- 또는 MyBatis -->
 <dependency>
     <groupId>kr.devslab</groupId>
     <artifactId>api-log-mybatis</artifactId>
-    <version>0.6.0</version>
+    <version>3.0.0</version>
 </dependency>
 ```
 

README.md

@@ -72,7 +72,7 @@ ApiEventListener  (api-log-core)
 
 ## Installation
 
-v0.6.0 splits the starter into four artifacts: a backend-agnostic core, plus
+v3.0.0 splits the starter into four artifacts: a backend-agnostic core, plus
 one of three persistence backends. Add **`api-log-core` plus exactly one
 backend** to your build:
 
@@ -92,21 +92,21 @@ coordinate is enough.
 <dependency>
     <groupId>kr.devslab</groupId>
     <artifactId>api-log-jpa</artifactId>
-    <version>0.6.0</version>
+    <version>3.0.0</version>
 </dependency>
 
 <!-- ...or R2DBC for reactive apps -->
 <dependency>
     <groupId>kr.devslab</groupId>
     <artifactId>api-log-r2dbc</artifactId>
-    <version>0.6.0</version>
+    <version>3.0.0</version>
 </dependency>
 
 <!-- ...or MyBatis -->
 <dependency>
     <groupId>kr.devslab</groupId>
     <artifactId>api-log-mybatis</artifactId>
-    <version>0.6.0</version>
+    <version>3.0.0</version>
 </dependency>
 ```
 

docs/changelog.ko.md

@@ -266,7 +266,9 @@ v0.1.0의 자동 마이그레이션에 의존하고 있었다면:
 - `ApiLogAutoConfiguration`을 통한 자동 구성, `@ConditionalOnMissingBean` 오버라이드.
 - 서비스·리포지토리·리스너·Testcontainers 기반 PostgreSQL 통합까지 포괄적 테스트.
 
-[Unreleased]: https://github.com/devslab-kr/api-log/compare/v0.5.2...HEAD
+[Unreleased]: https://github.com/devslab-kr/api-log/compare/v3.0.0...HEAD
+[3.0.0]: https://github.com/devslab-kr/api-log/releases/tag/v3.0.0
+[0.6.0]: https://github.com/devslab-kr/api-log/releases/tag/v0.6.0
 [0.5.2]: https://github.com/devslab-kr/api-log/releases/tag/v0.5.2
 [0.5.1]: https://github.com/devslab-kr/api-log/releases/tag/v0.5.1
 [0.5.0]: https://github.com/devslab-kr/api-log/releases/tag/v0.5.0

docs/changelog.md

@@ -266,7 +266,9 @@ First public release. Repackaged as a standalone Spring Boot starter.
 - Auto-configuration via `ApiLogAutoConfiguration` with `@ConditionalOnMissingBean` overrides.
 - comprehensive test suite covering services, repository, listener, and Testcontainers-backed PostgreSQL integration.
 
-[Unreleased]: https://github.com/devslab-kr/api-log/compare/v0.5.2...HEAD
+[Unreleased]: https://github.com/devslab-kr/api-log/compare/v3.0.0...HEAD
+[3.0.0]: https://github.com/devslab-kr/api-log/releases/tag/v3.0.0
+[0.6.0]: https://github.com/devslab-kr/api-log/releases/tag/v0.6.0
 [0.5.2]: https://github.com/devslab-kr/api-log/releases/tag/v0.5.2
 [0.5.1]: https://github.com/devslab-kr/api-log/releases/tag/v0.5.1
 [0.5.0]: https://github.com/devslab-kr/api-log/releases/tag/v0.5.0

docs/getting-started/installation.ko.md

@@ -8,7 +8,7 @@
 
 ## 의존성 추가
 
-v0.6.0부터 스타터가 백엔드 비종속 코어 + 영속화 백엔드 1개로 분리됐습니다.
+v3.0.0부터 스타터가 백엔드 비종속 코어 + 영속화 백엔드 1개로 분리됐습니다.
 **아래 표에서 한 줄만 고르면 됩니다 — 해당 백엔드 아티팩트가
 `api-log-core`를 transitive하게 가져옵니다.**
 
@@ -25,21 +25,21 @@ v0.6.0부터 스타터가 백엔드 비종속 코어 + 영속화 백엔드 1개
     <dependency>
         <groupId>kr.devslab</groupId>
         <artifactId>api-log-jpa</artifactId>
-        <version>0.6.0</version>
+        <version>3.0.0</version>
     </dependency>
 
     <!-- 또는 리액티브 앱에서 -->
     <dependency>
         <groupId>kr.devslab</groupId>
         <artifactId>api-log-r2dbc</artifactId>
-        <version>0.6.0</version>
+        <version>3.0.0</version>
     </dependency>
 
     <!-- 또는 MyBatis -->
     <dependency>
         <groupId>kr.devslab</groupId>
         <artifactId>api-log-mybatis</artifactId>
-        <version>0.6.0</version>
+        <version>3.0.0</version>
     </dependency>
     ```
 
@@ -65,12 +65,12 @@ v0.6.0부터 스타터가 백엔드 비종속 코어 + 영속화 백엔드 1개
     ```
 
 !!! tip "최신 버전"
-    `0.6.0`은 [Maven Central](https://central.sonatype.com/artifact/kr.devslab/api-log-core)의 최신 버전으로 교체.
+    `3.0.0`은 [Maven Central](https://central.sonatype.com/artifact/kr.devslab/api-log-core)의 최신 버전으로 교체.
 
 !!! info "v0.5.x에서 업그레이드?"
     기존 `api-log-spring-boot-starter` 좌표를 `api-log-jpa`로 바꾸면 됩니다
     (동일 JPA 백엔드, 동일 `api_log` 행). 일부 패키지 이름이 바뀌었으니
-    [v0.6.0 변경 이력](../changelog.md#060--멀티모듈-분리-gradle-jpa--r2dbc--mybatis-백엔드-선택-지원)에서
+    [v3.0.0 변경 이력](../changelog.md#060--멀티모듈-분리-gradle-jpa--r2dbc--mybatis-백엔드-선택-지원)에서
     매핑 표 참고.
 
 ## 각 아티팩트가 가져오는 의존성

docs/getting-started/installation.md

@@ -8,7 +8,7 @@
 
 ## Adding the dependency
 
-v0.6.0 splits the starter into a backend-agnostic core plus one persistence
+v3.0.0 splits the starter into a backend-agnostic core plus one persistence
 backend per artifact. **Pick one row from the table below — that's it; the
 backend artifact pulls in `api-log-core` transitively.**
 
@@ -25,21 +25,21 @@ backend artifact pulls in `api-log-core` transitively.**
     <dependency>
         <groupId>kr.devslab</groupId>
         <artifactId>api-log-jpa</artifactId>
-        <version>0.6.0</version>
+        <version>3.0.0</version>
     </dependency>
 
     <!-- ...or, for reactive apps -->
     <dependency>
         <groupId>kr.devslab</groupId>
         <artifactId>api-log-r2dbc</artifactId>
-        <version>0.6.0</version>
+        <version>3.0.0</version>
     </dependency>
 
     <!-- ...or, MyBatis -->
     <dependency>
         <groupId>kr.devslab</groupId>
         <artifactId>api-log-mybatis</artifactId>
-        <version>0.6.0</version>
+        <version>3.0.0</version>
     </dependency>
     ```
 
@@ -65,12 +65,12 @@ backend artifact pulls in `api-log-core` transitively.**
     ```
 
 !!! tip "Latest version"
-    Replace `0.6.0` with the latest from [Maven Central](https://central.sonatype.com/artifact/kr.devslab/api-log-core).
+    Replace `3.0.0` with the latest from [Maven Central](https://central.sonatype.com/artifact/kr.devslab/api-log-core).
 
 !!! info "Upgrading from v0.5.x?"
     Swap the old `api-log-spring-boot-starter` coordinate for `api-log-jpa`
     (same JPA backend, same `api_log` rows). A few packages were renamed —
-    see the [v0.6.0 changelog](../changelog.md#060--multi-module-split-gradle-pluggable-jpa--r2dbc--mybatis-backends)
+    see the [v3.0.0 changelog](../changelog.md#060--multi-module-split-gradle-pluggable-jpa--r2dbc--mybatis-backends)
     for the complete mapping.
 
 ## What each artifact pulls in

docs/guides/jpa-backend.ko.md

@@ -23,7 +23,7 @@ WebFlux + R2DBC 환경이면 [`api-log-r2dbc`](r2dbc-backend.md), MyBatis 환경
     <dependency>
         <groupId>kr.devslab</groupId>
         <artifactId>api-log-jpa</artifactId>
-        <version>0.6.0</version>
+        <version>3.0.0</version>
     </dependency>
     ```
 

docs/guides/jpa-backend.md

@@ -25,7 +25,7 @@ you're on MyBatis, prefer [`api-log-mybatis`](mybatis-backend.md). The
     <dependency>
         <groupId>kr.devslab</groupId>
         <artifactId>api-log-jpa</artifactId>
-        <version>0.6.0</version>
+        <version>3.0.0</version>
     </dependency>
     ```
 

docs/guides/mybatis-backend.ko.md

@@ -23,7 +23,7 @@ JPA를 쓰고 있으면 [`api-log-jpa`](jpa-backend.md) 선택. WebFlux + R2DBC
     <dependency>
         <groupId>kr.devslab</groupId>
         <artifactId>api-log-mybatis</artifactId>
-        <version>0.6.0</version>
+        <version>3.0.0</version>
     </dependency>
     ```
 

docs/guides/mybatis-backend.md

@@ -24,7 +24,7 @@ is identical across all three.
     <dependency>
         <groupId>kr.devslab</groupId>
         <artifactId>api-log-mybatis</artifactId>
-        <version>0.6.0</version>
+        <version>3.0.0</version>
     </dependency>
     ```
 

docs/guides/r2dbc-backend.ko.md

@@ -23,7 +23,7 @@ Servlet 스택이라면 JPA가 더 자연스럽습니다 — [`api-log-jpa`](jpa
     <dependency>
         <groupId>kr.devslab</groupId>
         <artifactId>api-log-r2dbc</artifactId>
-        <version>0.6.0</version>
+        <version>3.0.0</version>
     </dependency>
     ```
 
@@ -61,7 +61,7 @@ spring:
 | `ApiLogR2dbcSchemaInitializer` | Spring Boot의 `R2dbcScriptDatabaseInitializer`로 `V1.0__create_api_log.sql`을 리액티브하게 실행 (BUILTIN 모드만) |
 
 스키마 초기화는 `ConnectionFactory`와만 통신합니다 — **JDBC DataSource가
-필요 없음**, 부팅 시에도. v0.6.0에서 이 백엔드가 약속하는 핵심:
+필요 없음**, 부팅 시에도. v3.0.0에서 이 백엔드가 약속하는 핵심:
 완전 리액티브 `api_log` 설치.
 
 ## 행이 어떻게 써지는가

docs/guides/r2dbc-backend.md

@@ -25,7 +25,7 @@ rows in `api_log`.
     <dependency>
         <groupId>kr.devslab</groupId>
         <artifactId>api-log-r2dbc</artifactId>
-        <version>0.6.0</version>
+        <version>3.0.0</version>
     </dependency>
     ```
 
@@ -63,7 +63,7 @@ When `ConnectionFactory` is on the classpath and `api.log.enabled=true`,
 | `ApiLogR2dbcSchemaInitializer` | Runs `V1.0__create_api_log.sql` reactively via Spring Boot's `R2dbcScriptDatabaseInitializer` (BUILTIN mode only) |
 
 The schema initializer talks to `ConnectionFactory` directly — **no JDBC
-DataSource is required**, even at boot. That's the v0.6.0 promise this
+DataSource is required**, even at boot. That's the v3.0.0 promise this
 backend delivers: a fully reactive `api_log` install.
 
 ## How rows get written