docs(profile): fix api-log badge artifact ID + versioning policy note#8
Closed
jlc488 wants to merge 1 commit into
Closed
docs(profile): fix api-log badge artifact ID + versioning policy note#8jlc488 wants to merge 1 commit into
jlc488 wants to merge 1 commit into
Conversation
The api-log Maven Central badge URL was pointed at \`kr.devslab/api-log\`
— a coordinate that doesn't exist (the published artifacts are
\`api-log-core\`, \`-jpa\`, \`-r2dbc\`, \`-mybatis\`). The badge currently
shows "no version found" instead of the published version.
Repoint to \`kr.devslab/api-log-core\` (the core module that every
backend depends on) so the badge displays the active version. Same
artifact line — all 4 modules ship at the same coordinate version.
Once the 3.0.0 renumber lands on Maven Central, the badge will pick
it up automatically.
Also adds the same versioning-policy sentence used on the other libs
("Library major matches the Spring Boot major it targets").
Contributor
Author
|
Closing — user is making related badge changes elsewhere. Will revisit after their changes land if anything in this PR is still relevant. |
jlc488
added a commit
that referenced
this pull request
May 23, 2026
…tral coordinate) The api-log badge URL was pointing at `kr.devslab/api-log` — a coordinate that doesn't exist. api-log has been multi-module since 0.6.0; the published artifacts are `api-log-core`, `-jpa`, `-r2dbc`, `-mybatis`. The badge was rendering "no version found." Caught by an in-flight #8 (closed in favor of folding the fix into this branch, since both PRs touched the same line and #6 was the active badge-conversion branch). Changes: - badge URL: kr.devslab/api-log → kr.devslab/api-log-core - label: kr.devslab:api-log → kr.devslab:api-log-* (wildcard communicates "all four modules ship at one version") - link: central.sonatype.com/artifact/kr.devslab/api-log → ../api-log-core (the broken link was a side effect of the same root cause) - prose: added "all modules ship at the same version" to the module-split note, so readers don't wonder why the badge label has a `*` After the api-log 3.0.0 renumber publishes to Maven Central (api-log#2 merged, tag pending), the badge will resolve to 3.0.0 automatically. No further README edits needed for patch releases.
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 api-log Maven Central badge URL was pointed at
kr.devslab/api-log— a coordinate that doesn't exist. The published artifacts areapi-log-core,-jpa,-r2dbc,-mybatis(multi-module split since 0.6.0). The badge has been showing "no version found" instead of the live version.This PR:
kr.devslab/api-log-core(the core module every backend depends on) so the badge actually renders.kr.devslab:api-log-*(with the wildcard) to communicate that all 4 modules ship at the same version.After the api-log 3.0.0 renumber lands on Maven Central (currently in flight — api-log#2 merged, tag
v3.0.0pushed, release workflow running), the badge will pick up3.0.0automatically. No further changes to this README needed when patches ship.Related
devslab-kr/.github/.github/VERSIONING.md