Skip to content

ignore pac4j Dependabot bumps pending upstream fix - #781

Merged
jtnord merged 2 commits into
jenkinsci:mainfrom
nevingeorgesunny:ignore-pac4j-dependabot-bumps
Aug 4, 2026
Merged

ignore pac4j Dependabot bumps pending upstream fix#781
jtnord merged 2 commits into
jenkinsci:mainfrom
nevingeorgesunny:ignore-pac4j-dependabot-bumps

Conversation

@nevingeorgesunny

@nevingeorgesunny nevingeorgesunny commented Jul 31, 2026

Copy link
Copy Markdown

What

Adds a Dependabot ignore rule for all org.pac4j:* dependencies to prevent
automated bumps to pac4j 6.5.x and above.

compliments #767 (review)

Why

pac4j commit a0fbdd610b ("rework build", April 2026) moved 12 test utility
classes from src/test/java into src/main/java, causing them to ship inside
the production

saml-plugin is currently on pac4j 6.4.1 which predates this change and is
not affected. The ignore rule prevents Dependabot from bumping to 6.5.0+
until the upstream fix is in place.

@nevingeorgesunny nevingeorgesunny changed the title chore: ignore pac4j Dependabot bumps pending upstream fix ignore pac4j Dependabot bumps pending upstream fix Jul 31, 2026
@nevingeorgesunny
nevingeorgesunny marked this pull request as ready for review July 31, 2026 11:49
@nevingeorgesunny
nevingeorgesunny requested a review from a team as a code owner July 31, 2026 11:49
@jtnord
jtnord merged commit e34f2b4 into jenkinsci:main Aug 4, 2026
17 checks passed
@jglick

jglick commented Aug 4, 2026

Copy link
Copy Markdown
Member

For this kind of situation I recommend creating a draft PR reverting the exclusion, to serve as a reminder to future maintainers to revisit. Otherwise the pac4j problem might get fixed, nobody here gets the notification, nobody remembers to revert the exclusion, and we do not get updates for years until someone is pestered by a CVE notification and wonders why there are no Dependabot PRs picking up the fix.

@nevingeorgesunny

Copy link
Copy Markdown
Author

For this kind of situation I recommend creating a draft PR reverting the exclusion ...

#784

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.

3 participants