Skip to content

Update json4s-core, json4s-native to 4.1.0#2705

Closed
softwaremill-ci wants to merge 1 commit into
masterfrom
update/json4s-core-4.1.0
Closed

Update json4s-core, json4s-native to 4.1.0#2705
softwaremill-ci wants to merge 1 commit into
masterfrom
update/json4s-core-4.1.0

Conversation

@softwaremill-ci
Copy link
Copy Markdown
Contributor

About this PR

📦 Updates

  • org.json4s:json4s-core
  • org.json4s:json4s-native

from 4.0.7 to 4.1.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!

🔍 Files still referring to the old version number

The following files still refer to the old version number (4.0.7).
You might want to review and update them manually.

examples/src/main/scala/sttp/client4/examples/json/getAndParseJsonPekkoHttpJson4s.scala
⚙ Adjust future updates

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

updates.ignore = [ { groupId = "org.json4s" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.json4s" }
}]
labels: library-update, early-semver-minor, semver-spec-minor, artifact-migrations, old-version-remains, commit-count:1

@adamw
Copy link
Copy Markdown
Member

adamw commented May 29, 2026

Won't merge: json4s has no stable 4.1.0 release — only milestones 4.1.0-M1..M8 exist on Maven Central, so the dependency doesn't resolve. Latest stable remains 4.0.x.

@adamw adamw closed this May 29, 2026
@softwaremill-ci softwaremill-ci deleted the update/json4s-core-4.1.0 branch May 30, 2026 01:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants