Bump org.postgresql:postgresql to 42.7.11#12403
Merged
tdonohue merged 3 commits intoDSpace:mainfrom May 5, 2026
Merged
Conversation
This was only pinned to avoid dependency convergence issues between org.postgresql:postgresql and org.apache.solr:solr-core, but as of version 42.7.11, org.postgresql:postgresql no longer depends on it.
Both com.google.guava:guava and org.apache.solr:solr-core depend on org.checkerframework:checker-qual, but org.postgresql:postgresql no longer does.
Contributor
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin dspace-7_x
git worktree add -d .worktree/backport-12403-to-dspace-7_x origin/dspace-7_x
cd .worktree/backport-12403-to-dspace-7_x
git switch --create backport-12403-to-dspace-7_x
git cherry-pick -x 4494b7668697cf8a3783911ffc5b7d5506b57514 0cdde40242be6348f276e43d9967c3d0bbfaccb3 3c9c60c61f9d33868ca2ee2f786532eafa9a8149 |
Contributor
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin dspace-8_x
git worktree add -d .worktree/backport-12403-to-dspace-8_x origin/dspace-8_x
cd .worktree/backport-12403-to-dspace-8_x
git switch --create backport-12403-to-dspace-8_x
git cherry-pick -x 4494b7668697cf8a3783911ffc5b7d5506b57514 0cdde40242be6348f276e43d9967c3d0bbfaccb3 3c9c60c61f9d33868ca2ee2f786532eafa9a8149 |
Contributor
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin dspace-9_x
git worktree add -d .worktree/backport-12403-to-dspace-9_x origin/dspace-9_x
cd .worktree/backport-12403-to-dspace-9_x
git switch --create backport-12403-to-dspace-9_x
git cherry-pick -x 4494b7668697cf8a3783911ffc5b7d5506b57514 0cdde40242be6348f276e43d9967c3d0bbfaccb3 3c9c60c61f9d33868ca2ee2f786532eafa9a8149 |
Member
|
@alanorth : It looks like this was unable to be automatically backported to 9.x, 8.x and 7.x. Would you be able to make backport PR(s) for this? |
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
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.
References
Add references/links to any related issues or PRs. These may include:
Description
Bump the bump
org.postgresql:postgresqldependency to 42.7.11.As a bonus, we can remove the explicit dependency on
org.checkerframework:checker-qualbecauseorg.postgresql:postgresqlno longer depends on it, which means we do not need to solve that particular dependency convergence issue anymore.Instructions for Reviewers
Please add a more detailed description of the changes made by your PR. At a minimum, providing a bulleted list of changes in your PR is helpful to reviewers.
List of changes in this PR:
org.checkerframework:checker-qualdependencypom.xmlInclude guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!
mainbranch of code (unless it is a backport or is fixing an issue specific to an older branch).pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.