Skip to content

chore(renovate): pin DataTables webjars as a coordinated set - #374

Open
Naenyn wants to merge 1 commit into
uPortal-Project:masterfrom
Naenyn:chore/renovate-pin-datatables
Open

Naenyn wants to merge 1 commit into
uPortal-Project:masterfrom
Naenyn:chore/renovate-pin-datatables

Conversation

@Naenyn

@Naenyn Naenyn commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Renovate proposed bumping datatables.net-select to v4 (see #371). It fails to resolve because the DataTables webjars are a coordinated set with peer-dependency version ranges across the core and extensions:

Could not resolve version conflict among [
  datatables.net-bs5:2.3.8,
  datatables.net-searchpanes-bs5:2.3.5 -> datatables.net-bs5:[2.0.0,3.0.0-0),
  datatables.net-select-bs5:4.1.0      -> datatables.net-bs5:[3.1.0,4.0.0-0)
]

select v4 wants core (datatables.net-bs5) 3.x, but the core is pinned at 2.3.8 and searchpanes requires core 2.x — non-overlapping ranges, so Maven can't pick a single core version.

Change

Add two renovate.json rules to keep the six DataTables webjars (core, -bs5, searchpanes(+bs5), select(+bs5)) as a coordinated set:

  • datatables.net, datatables.net-bs5, datatables.net-searchpanes, datatables.net-searchpanes-bs5 → < 3.0.0
  • datatables.net-select, datatables.net-select-bs5 → < 4.0.0

This stops Renovate from proposing partial cross-major bumps of individual DataTables artifacts. A move to DataTables 3.x+ needs to bump all six together, coordinated with the consuming uPortal skin (see also the parked DataTables v3 PR #366).

Notes

Renovate proposed bumping datatables.net-select to v4 (see uPortal-Project#371), which
fails to resolve: select v4 requires datatables.net-bs5 [3.1.0,4.0.0),
but the core is on 2.3.8 and searchpanes requires [2.0.0,3.0.0) — the
ranges do not overlap, so Maven cannot pick a single core version.

The six DataTables webjars (core, bs5, searchpanes, select, each in
plain + bs5) are a coordinated set whose extensions peer-depend on a
compatible core range. No single piece can cross a major boundary while
the others stay behind. Cap core + searchpanes at < 3.0.0 and select at
< 4.0.0 so Renovate stops proposing partial cross-major bumps; a move to
DataTables 3.x+ must bump all six together alongside the consuming
uPortal skin.
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