Skip to content

easy-paging 0.4.0/0.5.0 → 3.0.0/4.0.0 (versioning policy adoption)#57

Merged
jlc488 merged 1 commit into
mainfrom
easy-paging-versioning-policy-bump
May 23, 2026
Merged

easy-paging 0.4.0/0.5.0 → 3.0.0/4.0.0 (versioning policy adoption)#57
jlc488 merged 1 commit into
mainfrom
easy-paging-versioning-policy-bump

Conversation

@jlc488
Copy link
Copy Markdown
Contributor

@jlc488 jlc488 commented May 23, 2026

Summary

Adopts the new Spring-major-aligned versioning policy for the 8 easy-paging demos:

  • SB3 demos (easy-paging-demo, easy-paging-keyset-demo, easy-paging-postgres-demo, easy-paging-reactive-demo) — 0.4.03.0.0
  • SB4 demos (easy-paging-sb4-demo, easy-paging-sb4-keyset-demo, easy-paging-sb4-postgres-demo, easy-paging-sb4-reactive-demo) — 0.5.04.0.0
  • Top-level README.{md,ko.md} — version coordinates updated

Also simplifies .github/dependabot.yml: since the library major now matches the Spring Boot major, the standard update-types: ["version-update:semver-major"] ignore does the right thing automatically. The versions: [">= 0.5"] workaround from #54 is no longer needed.

Maven Central artifacts

All 4 verified live (curl -sI ... | grep 200):

Test plan

  • CI re-runs the 8 changed-demo builds against the new coordinates
  • After merge: branch rename in easy-paging-spring-boot-starter (0.4.x3.x)

Related

The easy-paging starter renumbered to align with the Spring Boot major
it targets (https://github.com/devslab-kr/.github/blob/main/.github/VERSIONING.md):

- SB3 maintenance line: 0.4.0 → 3.0.0
- SB4 active line:      0.5.0 → 4.0.0

This commit bumps the 8 easy-paging demos in lockstep:

- easy-paging-{demo,keyset,postgres,reactive}-demo → 3.0.0
- easy-paging-sb4-{demo,keyset,postgres,reactive}-demo → 4.0.0
- top-level README.{md,ko.md} version coordinates

Also simplifies .github/dependabot.yml: now that the library major
matches the Spring Boot major, the standard `semver-major` ignore does
the right thing automatically and the `versions: [">= 0.5"]` filter
from PR #54 is no longer needed (would have only ever held until the
next SB4-only major release of easy-paging anyway, and that's now
explicitly held by `semver-major`).

Verified all 4 artifacts live on Maven Central:
  - easy-paging-spring-boot-starter:4.0.0
  - easy-paging-spring-boot-starter:3.0.0
  - easy-paging-spring-boot-starter-reactive:4.0.0
  - easy-paging-spring-boot-starter-reactive:3.0.0
@jlc488 jlc488 merged commit 1553cca into main May 23, 2026
10 checks passed
jlc488 added a commit 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)
      → [![Maven Central](shields.io/maven-central/v/...?...&versionPrefix=N)](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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant