docs(readmes): badge-ify root tables (post-renumber)#59
Merged
Conversation
…nded 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.
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
Replaced the hardcoded version strings in all 3 root-README tables (14 demo rows × 2 languages) with shields.io Maven Central badges. Plus the section headers + maintenance-branch link that #57 didn't touch.
Spring Boot 4 (\0.5.x` line)`Spring Boot 4 (\4.x` line)`Spring Boot 3 maintenance (\0.4.x` line)`Spring Boot 3 maintenance (\3.x` line)`[\0.4.x` branch](.../tree/0.4.x)`[\3.x` branch](.../tree/3.x)`Maven Central coordinatesMaven Central[\kr.devslab:...:N.N.N`](sonatype)`[](sonatype)Why this PR exists (and why a second time)
This is the redo of #56, which was closed because it used 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` per the new Spring-major-aligned versioning policy), this PR finishes the badge conversion with the correct `versionPrefix=3` / `=4`.
Why per-line `versionPrefix` matters
Without the filter, the SB3 maintenance row's badge would jump to the latest `4.x` patch the moment one shipped — hiding the maintenance line's actual state. With `versionPrefix=3` on SB3 rows and `versionPrefix=4` on SB4 rows, each line independently tracks its own latest.
ssrf-guard rows use no prefix (single-line library, no SB4 fork yet).
Auto-update demonstration (already in production)
Profile badges merged 13:40Z (#6 on org `.github`). api-log v3.0.0 published to Maven Central 13:44Z (release workflow triggered by tag push). Profile's api-log badge picked up the new version within minutes — zero manual README edits required.
Same behavior will apply here on the next easy-paging patch release.
What's NOT in this PR
Test plan