Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Update rdf4j-queryparser-sparql from 4.3.12 to 5.0.0 #1924

Closed
wants to merge 1 commit into from

Conversation

RenkuBot
Copy link
Collaborator

About this PR

πŸ“¦ Updates org.eclipse.rdf4j:rdf4j-queryparser-sparql from 4.3.12 to 5.0.0 ⚠

Usage

βœ… Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

βš™ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.eclipse.rdf4j", artifactId = "rdf4j-queryparser-sparql" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.eclipse.rdf4j", artifactId = "rdf4j-queryparser-sparql" }
}]
labels: library-update, early-semver-major, semver-spec-major, commit-count:1

@RenkuBot RenkuBot requested a review from a team as a code owner June 22, 2024 06:02
@RenkuBot RenkuBot force-pushed the update/rdf4j-queryparser-sparql-5.0.0 branch from d7dbe1e to 13bf5da Compare July 10, 2024 06:02
@RenkuBot
Copy link
Collaborator Author

Superseded by #1933.

@RenkuBot RenkuBot closed this Jul 11, 2024
@RenkuBot RenkuBot deleted the update/rdf4j-queryparser-sparql-5.0.0 branch July 11, 2024 06:01
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