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

bump: mssql-jdbc 7.4.1.jre12 (was 7.4.1.jre8) #527

Closed

Conversation

scala-steward
Copy link
Contributor

About this PR

πŸ“¦ Updates com.microsoft.sqlserver:mssql-jdbc from 7.4.1.jre8 to 7.4.1.jre12

πŸ“œ Changelog

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 = "com.microsoft.sqlserver", artifactId = "mssql-jdbc" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.microsoft.sqlserver", artifactId = "mssql-jdbc" }
}]
labels: test-library-update, commit-count:1

@johanandren
Copy link
Member

We still support Java 11 so I expect this is a no-go

@sebastian-alfers
Copy link
Contributor

Is is possible to exclude this from scala-steward?

@johanandren
Copy link
Member

Yeah, we could create a .scala-steward.conf and pin it to 7.4.1.jre8, but then we wouldn't get an autobump if a 7.4.2.jre8 was released I guess.

@johanandren johanandren closed this May 3, 2024
@scala-steward scala-steward deleted the update/mssql-jdbc-7.4.1.jre12 branch May 5, 2024 03:53
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