Skip to content

build(deps): hold easy-paging at < 0.5 in the SB3 demo block#54

Merged
jlc488 merged 1 commit into
mainfrom
dependabot-pin-easy-paging-sb3
May 23, 2026
Merged

build(deps): hold easy-paging at < 0.5 in the SB3 demo block#54
jlc488 merged 1 commit into
mainfrom
dependabot-pin-easy-paging-sb3

Conversation

@jlc488
Copy link
Copy Markdown
Contributor

@jlc488 jlc488 commented May 23, 2026

Summary

Stops Dependabot from bumping kr.devslab:easy-paging-spring-boot-starter past 0.4.x in the four SB3 demos (easy-paging-demo, easy-paging-keyset-demo, easy-paging-postgres-demo, easy-paging-reactive-demo).

Problem

Dependabot opened #50 bumping easy-paging 0.4.0 → 0.5.0 in the SB3 demos. CI went red on all four — 0.5.0 is the SB4 release line (Spring Framework 7 / Jackson 3) and the SB3 demos pin Spring Boot 3.5.x.

The existing ignore rule

- dependency-name: "kr.devslab:easy-paging-spring-boot-starter"
  update-types: ["version-update:semver-major"]

didn't catch it because the starter is pre-1.0: 0.4 → 0.5 reads to Dependabot as a minor bump even though it's effectively the SB3 → SB4 release-line jump in this codebase.

Fix

Replace the major-only ignore with an explicit versions: filter on both easy-paging artifacts:

- dependency-name: "kr.devslab:easy-paging-spring-boot-starter"
  versions: [">= 0.5"]
- dependency-name: "kr.devslab:easy-paging-spring-boot-starter-reactive"
  versions: [">= 0.5"]
  • 0.4.x patches still flow to the SB3 demos
  • 0.5+ stays blocked
  • The SB4 demos under /easy-paging-sb4-*/ have no such ignore and continue to track the 0.5.x line

Follow-up

After this merges, close #50 (PR will be a no-op against the new policy anyway, since Dependabot won't reopen).

Test plan

  • CI passes on this PR (only .github/dependabot.yml touched — no demo builds triggered)
  • After merge, manual sanity check: Dependabot run does not reopen the 0.5.0 bump for SB3 demos

Dependabot opened #50 trying to bump easy-paging 0.4.0 → 0.5.0 across the
four SB3 demos. Build went red on all four — 0.5.0 is the SB4 release line
and the SB3 demos pin Spring Boot 3.5.x, so the starter's new
Spring-Framework-7 / Jackson-3 baseline can't load.

The existing `update-types: ["version-update:semver-major"]` ignore
didn't catch this because the starter is pre-1.0: 0.4 → 0.5 reads as a
minor bump to Dependabot even though it's effectively the SB3 → SB4
release-line jump for us.

Replace the major-only ignore with an explicit `versions: [">= 0.5"]`
filter on both easy-paging artifacts. 0.4.x patches will still flow
to the SB3 demos; 0.5+ stays blocked. The SB4 demos under
/easy-paging-sb4-*/ already have no such ignore and continue to track
the 0.5.x line.

Closes PR #50.
@jlc488 jlc488 merged commit b67e430 into main May 23, 2026
3 checks passed
jlc488 added a commit that referenced this pull request May 23, 2026
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
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