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

Update upickle to 4.0.1 #115

Closed
wants to merge 1 commit into from
Closed

Conversation

tarao-scala-steward[bot]
Copy link
Contributor

About this PR

πŸ“¦ Updates com.lihaoyi:upickle from 3.3.1 to 4.0.1 ⚠

πŸ“œ GitHub Release Notes - Release Notes - Version Diff

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.lihaoyi", artifactId = "upickle" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.lihaoyi", artifactId = "upickle" }
}]
labels: library-update, early-semver-major, semver-spec-major, version-scheme:semver-spec, commit-count:1

@tarao-scala-steward tarao-scala-steward bot force-pushed the update/upickle-4.0.1 branch 2 times, most recently from ba8c315 to 0ba33c9 Compare September 1, 2024 00:33
@tarao
Copy link
Owner

tarao commented Sep 16, 2024

#108

@tarao-scala-steward
Copy link
Contributor Author

Superseded by #122.

@tarao-scala-steward tarao-scala-steward bot deleted the update/upickle-4.0.1 branch September 29, 2024 00:33
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