Renumber 0.6.0 → 3.0.0 per Spring-major-aligned versioning policy#2
Merged
Conversation
Adopts the new org-level policy documented at https://github.com/devslab-kr/.github/blob/main/.github/VERSIONING.md: the library's major version number matches the Spring Boot major it targets. api-log targets Spring Boot 3, so the next release ships as 3.0.0 (renumbering of what would have been 0.6.1 / 0.7.0). Motivation: devslab-examples PR #50 (Dependabot bumped easy-paging 0.4.0 → 0.5.0 across the SB3 demos because pre-1.0 versioning + Spring-major coupling makes \`minor\` bumps actually-major). Aligning library majors with Spring Boot majors makes the standard \`semver-major\` ignore rule do the right thing automatically, and gives consumers a one-glance answer to "which version targets which Spring Boot major". No code, no API, no dependency changes — same Spring Boot 3 baseline, same ApiLogWriter SPI, same auto-config. Published JAR bytes are identical to 0.6.0 apart from the version coordinate. Files touched: - gradle.properties: VERSION=0.6.0-SNAPSHOT → 3.0.0 - CHANGELOG.md + docs/changelog.{md,ko.md}: [3.0.0] entry above [0.6.0] - README.{md,ko.md}: install snippets bumped - docs/getting-started/installation.{md,ko.md}: Gradle (Kotlin & Groovy) + Maven snippets bumped - docs/guides/{jpa,r2dbc,mybatis}-backend.{md,ko.md}: install snippets Previous 0.6.0 artifacts remain on Maven Central as historical references. When a Spring Boot 4 line ships, it will be 4.x.y.
This was referenced May 23, 2026
jlc488
added a commit
that referenced
this pull request
May 23, 2026
PR #2 renumbered the artifact coordinates 0.6.0 → 3.0.0 to align with the new Spring-major-aligned versioning policy, but the doc surfaces that quote the version in install snippets / prose were left at 0.6.0. Readers landing on README or the docs site would copy-paste a dead version coordinate. Updated in this PR: - README.md + README.ko.md * "v0.6.0 splits the starter..." prose → "v3.0.0..." * 3 Maven <version>0.6.0</version> snippets per file → 3.0.0 * (Gradle snippet was already on 3.0.0 — half-migrated state cleaned up) - docs/getting-started/installation.{md,ko.md} * Same prose + 3 Maven snippets + "Replace `0.6.0` with the latest" line bumped to 3.0.0 - docs/guides/{jpa,mybatis,r2dbc}-backend.{md,ko.md} * Each backend guide had a per-backend install snippet at 0.6.0 - docs/changelog.{md,ko.md} * [Unreleased] compare link updated v0.5.2...HEAD → v3.0.0...HEAD * Added [3.0.0] and [0.6.0] link references (the root CHANGELOG.md already had these — keeping the two changelogs in sync) Explicitly NOT changed (historical references): - CHANGELOG entries for [0.6.0], [0.5.x], etc. — these document what shipped at each version and stay as-is - The [3.0.0] entry's "Renumbering of 0.6.0" header — accurate statement of what 3.0.0 is Once api-log v3.0.0 is published to Maven Central (tag push pending), all install snippets and badge links in this PR resolve correctly.
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
1 participant
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
Adopts the new org-level Spring-major-aligned versioning policy: a library's major version number matches the Spring Boot major it targets. api-log targets Spring Boot 3, so the next release ships as
3.0.0.Why now
devslab-examplesPR #50 (two days ago) — Dependabot tried to bumpeasy-paging 0.4.0 → 0.5.0across the SB3 demos. CI went red because0.5.0was the SB4 release line. The pre-1.0 versioning made the Spring-major jump invisible to Dependabot'ssemver-majorignore. easy-paging just renumbered to align (0.4.0→3.0.0,0.5.0→4.0.0); ssrf-guard was already at3.xand naturally aligned. api-log is the lastkr.devslablibrary still on the pre-1.0 scheme.This PR renumbers
0.6.0-SNAPSHOT→3.0.0to fall in line.What changes
gradle.properties:VERSION=0.6.0-SNAPSHOT→3.0.0CHANGELOG.md+docs/changelog.{md,ko.md}: new[3.0.0]entry above[0.6.0]documenting the renumber, footer link addedREADME.{md,ko.md}: install snippets bumped to3.0.0docs/getting-started/installation.{md,ko.md}: Gradle Kotlin + Groovy + Maven snippets bumpeddocs/guides/{jpa,r2dbc,mybatis}-backend.{md,ko.md}: install snippets bumpedWhat does NOT change
ApiLogWriterSPI,ApiLogProperties, all auto-config beans — byte-identicalThe published
3.0.0JAR will be byte-identical to0.6.0apart from the<version>coordinate in the POM.Deployment plan (post-merge)
v3.0.0onmasterapi-log-core,-jpa,-r2dbc,-mybatis)README(devslab-kr/.github) bumped0.6.0→3.0.0Previous
0.6.0artifacts remain on Maven Central as historical references.Test plan
[3.0.0]entry after deploy3.0.0artifacts when the tag goes upRelated
devslab-kr/.github/.github/VERSIONING.md