ci(dependabot): ignore broken jackson-bom 2.22.0 + central-publishing 0.10.0#112
Merged
Merged
Conversation
… 0.10.0 Two grouped-PR poison-pills are tripping the maven-minor-patch group: - `com.fasterxml.jackson:jackson-bom 2.22.0` was published to Maven Central ahead of its module jars. `jackson-core-2.22.0.jar` currently returns 404 on `repo1.maven.org` — Sonatype partial-sync window. Until 2.22.1 (or 2.23.0) lands with full module sync, every grouped Dependabot PR that picks 2.22.0 fails CI at the dependency-resolution stage. - `org.sonatype.central:central-publishing-maven-plugin 0.10.0` is a 3-minor jump (0.7 → 0.10) on the plugin that pushes our Maven Central releases. The v1.6.6 cut used 0.7.0. We want to validate the release profile against 0.10.x in a focused PR, not let it ride along in a group bump that nobody is going to test against a real Central staging run. Adding both as explicit `ignore` entries (one specific version each) so Dependabot drops them from the grouped PR but still proposes future versions when they ship. Drop these entries once the upstream issues clear / the central-publishing 0.10.x evaluation lands.
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
PR #110 (the grouped maven-minor-patch Dependabot PR) is being blocked
by two specific upstream issues. Adding explicit
ignoreentries soDependabot drops them from the next grouped run while still picking up
future versions when they ship.
Why each version is ignored
jackson-bom 2.22.0— the BOM is on Maven Central but its modulejars aren't.
jackson-core-2.22.0.jarreturns HTTP 404 atrepo1.maven.org(Sonatype partial-sync window — BOM rolled aheadof its modules). Every grouped PR that picks 2.22.0 fails CI at
dependency resolution. Will drop this entry once 2.22.1 / 2.23.0
lands with full module sync.
central-publishing-maven-plugin 0.10.0— three-minor jump(0.7 → 0.10) on the plugin that pushes our Maven Central releases;
v1.6.6 cut used 0.7.0. Want to validate the release profile against
0.10.x in a focused PR with a real Sonatype staging run, not let it
ride along in a group bump.
After merge
@dependabot recreateon the closed PR) so the same group rebuilds with thesetwo skipped. The other 9 bumps — especially
logback-classic 1.5.34which fixes CVE-2026-9828
(deserialization whitelist bypass) — get a clean PR to merge.
Test plan
dependabot.ymlvalidates against the config schema(
dependency-nameisgroupId:artifactId,versions: ["..."]pins a specific release).
@dependabot recreate, confirmthe rebuilt PR drops jackson-bom 2.22.0 + central-publishing 0.10.0
while keeping the other 9 bumps.