docs: sweep stale 0.6.0 references after 3.0.0 renumber#3
Merged
Conversation
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.
jlc488
added a commit
to devslab-kr/devslab-examples
that referenced
this pull request
May 23, 2026
…nded (#59) Deferred from the earlier badge PR (#56, closed) — that one used the pre-renumber prefixes (versionPrefix=0.4 / 0.5). After #57 landed the renumber (easy-paging 0.4.0→3.0.0, 0.5.0→4.0.0), this PR finishes the badge conversion with the correct post-renumber prefixes. Changes per language (2 files, 40 lines each): Section headers — align with the renumber: "Spring Boot 4 (`0.5.x` line)" → "(`4.x` line)" "Spring Boot 3 maintenance (`0.4.x` line)" → "(`3.x` line)" Korean equivalents. Maintenance branch link — the branch was renamed too: [`0.4.x` branch](.../tree/0.4.x) → [`3.x` branch](.../tree/3.x) Column header — slight tightening since the cell content is now a badge instead of a coordinate string: "Maven Central coordinates" → "Maven Central" 14 rows — each "Maven Central coordinates" cell: [`kr.devslab:<artifact>:<version>`](sonatype-link) → [](sonatype-link) Where N = 4 for SB4 rows, N = 3 for SB3 rows. ssrf-guard rows use no prefix (single-line library; whatever's latest on Maven Central is what readers should pull). The versionPrefix filter keeps the two easy-paging lines visually independent — without it, the SB3 row's badge would jump to the latest 4.x patch the moment one ships. Per-demo README "Files of interest" tables intentionally left as prose (copy-paste-friendly Gradle snippets; #55 already aligned them with the build files). A CI mismatch check is a follow-up if those drift again. Sibling PRs in the same badge sweep, already merged: - devslab-kr/.github#6 (org profile) - devslab-kr/api-log#3 (api-log doc surface for 3.0.0 renumber) Maven Central propagation note: api-log v3.0.0 published 13:44Z, profile badge picked it up within minutes — same auto-update behavior will apply to these demos on the next easy-paging patch release.
4 tasks
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
PR #2 renumbered the artifact coordinates
0.6.0 → 3.0.0per the Spring-major-aligned versioning policy, but the doc surfaces that quote the version in install snippets / prose were left at0.6.0. Readers landing on the README or docs site would copy-paste a dead version coordinate.Files updated (12)
README.md/README.ko.md<version>0.6.0</version>snippets → 3.0.0. Gradle snippet was already on 3.0.0 — half-migrated state cleaned up.docs/getting-started/installation.md/.ko.md0.6.0with the latest" hint line.docs/guides/jpa-backend.md/.ko.mddocs/guides/mybatis-backend.md/.ko.mddocs/guides/r2dbc-backend.md/.ko.mddocs/changelog.md/.ko.md[Unreleased]compare linkv0.5.2...HEAD→v3.0.0...HEAD; added[3.0.0]and[0.6.0]link refs (rootCHANGELOG.mdalready had these — keeping the two changelogs in sync).Explicitly NOT changed
[0.6.0],[0.5.x], etc. — these document what shipped at each version and stay as-is.[3.0.0]entry's "Renumbering of0.6.0" header — accurate statement of what 3.0.0 is.Verification
No
0.6.0left in any current-state surface; only the changelog files retain it as historical record.Related
.github(PR #6) updated to point atapi-log-coreand uses the wildcard labelTest plan
api-log.devslab.krafter merge — install snippets show3.0.0, changelog footer links resolve to GitHub release pages (post v3.0.0 tag push)grep -rln "0\.6\.0" --include="*.md" .returns only the 3 changelog files