docs(profile): bump demo count 9 → 14 (post-SB4 + ssrf-guard expansion)#4
Merged
Conversation
The "(9 demos)" claim under the devslab-examples bullet predates two expansions that landed since the profile was last touched: - +4 easy-paging SB4 demos (PR devslab-examples#39) - +1 ssrf-guard-langchain4j-demo (PR devslab-examples#52) - the original 4 easy-paging SB3 + 5 ssrf-guard demos still ship → 14 demos total Replaced the bare count with a breakdown so the next reader can reconcile it against the repo without recounting, and so the next addition is more obviously a "bump the count + the breakdown" edit.
3 tasks
jlc488
added a commit
that referenced
this pull request
May 23, 2026
Open-source section under `// open source` was carrying hardcoded version strings for three of the four library entries — same drift pattern that just bit on devslab-examples and forced PR #3 here days after ssrf-guard 3.1.0 shipped. Replaced with shields.io badges sourced from Maven Central so the next release auto-updates the profile. Mappings: ssrf-guard → kr.devslab/ssrf-guard (no prefix; single line) easy-paging-starter → kr.devslab/easy-paging-spring-boot-starter × 2 badges: versionPrefix=4 (SB4 active), versionPrefix=3 (SB3 maintenance) api-log → kr.devslab/api-log (no prefix; SB3 only) The two easy-paging badges keep the SB4 / SB3 lines visually distinct — without the versionPrefix filter, the SB3 badge would jump to the SB4 latest version the moment a 4.x.y patch ships, hiding the maintenance line's actual state. devslab-examples row has no version to badge (it's a demo repo, not published), so the only change there (already in main) was the demo count breakdown from #4. Note on `versionPrefix=3` / `=4`: aligned with the new Spring-major-versioning policy (.github/VERSIONING.md). The easy-paging renumber 0.4.0 → 3.0.0 and 0.5.0 → 4.0.0 has already shipped to Maven Central, so the badges will resolve correctly on first render.
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
The devslab-examples bullet on the org profile says `(9 demos, bilingual READMEs)`, but the repo now ships 14 demos:
Replaced `9 demos` with a breakdown that reconciles to the repo at a glance:
Applied to both `README.md` and `README.ko.md`. Same pattern as the recent ssrf-guard 3.0.1 → 3.1.0 bump (#3) — these are doc surfaces that go stale whenever the underlying repos move.
Why the count drifted
Both expansions (#39, #52) updated the per-repo READMEs but not the org profile. This is the same class of slip that motivated `~/.claude/hooks/devslab-release-checklist.sh` — the local hook now mechanically reminds about the org profile surface on every `gh release create` / tag-push, so future bumps should be caught at release time rather than backfilled.
Test plan