docs(profile): fix api-log badge artifact ID + versioning policy note#10
Merged
Conversation
…note The Maven Central badge target \`kr.devslab/api-log\` doesn't exist as a published artifact — api-log ships as four coordinates (\`api-log-core\`, \`-jpa\`, \`-r2dbc\`, \`-mybatis\`) since the 0.6.0 multi-module split. The badge has been rendering as "maven-central: not found" since the badges PR (#6). Repoint to \`kr.devslab/api-log-core\` — the core module every backend artifact depends on — so the badge actually displays the active version. All 4 api-log artifacts ship at the same version line, so api-log-core's badge is representative of the whole family. Now correctly displays "maven-central: v3.0.0" after the recent renumber. Also adds the same versioning-policy sentence already on ssrf-guard and easy-paging, for consistency.
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 is currently rendering as "maven-central: not found" because its target —
kr.devslab/api-log— doesn't exist as a published artifact.api-log ships as four coordinates (since the 0.6.0 multi-module split):
kr.devslab:api-log-core(events, SPI, listener)kr.devslab:api-log-jpa(JPA backend)kr.devslab:api-log-r2dbc(R2DBC backend)kr.devslab:api-log-mybatis(MyBatis backend)This PR repoints the badge to
kr.devslab/api-log-core— the module every backend depends on — so it renders correctly. All 4 artifacts ship at the same version line (just released 3.0.0), soapi-log-core's badge is representative of the whole family.Before / after
Verified empirically by hitting the shields.io endpoint for each:
shields.io/maven-central/v/kr.devslab/api-log(current main)maven-central: not foundshields.io/maven-central/v/kr.devslab/api-log-core(this PR)maven-central: v3.0.0Also adds the same "Library major matches Spring Boot major" sentence already on the ssrf-guard / easy-paging lines, for consistency now that api-log adopted the policy.
Related
devslab-kr/.github/.github/VERSIONING.md