build: zio dependency updates

[lfdt-bot]

About this PR

Updates:

• 📦 dev.zio:zio from 2.1.24 to 2.1.26
  • 📜 GitHub Release Notes - Version Diff
• 📦 dev.zio:zio-config from 4.0.6 to 4.0.7
  • 📜 GitHub Release Notes - Version Diff
• 📦 dev.zio:zio-http from 3.7.4 to 3.11.1
  • 📜 GitHub Release Notes - Version Diff
• 📦 dev.zio:zio-json from 0.7.45 to 0.9.2
  • 📜 GitHub Release Notes - Version Diff
• 📦 dev.zio:zio-kafka from 3.2.0 to 3.4.0
  • 📜 GitHub Release Notes - Version Diff
• 📦 dev.zio:zio-logging from 2.5.2 to 2.5.3
  • 📜 GitHub Release Notes - Version Diff
• 📦 dev.zio:zio-prelude from 1.0.0-RC44 to 1.0.0-RC47
  • 📜 GitHub 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 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 numbers

The following files still refer to the old version numbers.
You might want to review and update them manually.

package-lock.json
.pre-commit-config.yaml
DEPENDENCIES.md
build.sbt
cloud-agent/client/generator/yarn.lock
tests/performance-tests/agent-performance-tests-k6/yarn.lock

⚙ Adjust future updates

Add these to your .scala-steward.conf file to ignore future updates of these dependencies:

updates.ignore = [
  { groupId = "dev.zio", artifactId = "zio" },
  { groupId = "dev.zio", artifactId = "zio-config" },
  { groupId = "dev.zio", artifactId = "zio-http" },
  { groupId = "dev.zio", artifactId = "zio-json" },
  { groupId = "dev.zio", artifactId = "zio-kafka" },
  { groupId = "dev.zio", artifactId = "zio-logging" },
  { groupId = "dev.zio", artifactId = "zio-prelude" }
]

Or, add these to slow down future updates of these dependencies:

dependencyOverrides = [
  {
    pullRequests = { frequency = "30 days" },
    dependency = { groupId = "dev.zio", artifactId = "zio" }
  },
  {
    pullRequests = { frequency = "30 days" },
    dependency = { groupId = "dev.zio", artifactId = "zio-config" }
  },
  {
    pullRequests = { frequency = "30 days" },
    dependency = { groupId = "dev.zio", artifactId = "zio-http" }
  },
  {
    pullRequests = { frequency = "30 days" },
    dependency = { groupId = "dev.zio", artifactId = "zio-json" }
  },
  {
    pullRequests = { frequency = "30 days" },
    dependency = { groupId = "dev.zio", artifactId = "zio-kafka" }
  },
  {
    pullRequests = { frequency = "30 days" },
    dependency = { groupId = "dev.zio", artifactId = "zio-logging" }
  },
  {
    pullRequests = { frequency = "30 days" },
    dependency = { groupId = "dev.zio", artifactId = "zio-prelude" }
  }
]

^{labels: library-update, test-library-update, early-semver-patch, semver-spec-patch, version-scheme:early-semver, early-semver-minor, semver-spec-minor, early-semver-major, early-semver-pre-release, semver-spec-pre-release, old-version-remains, commit-count:n:7}

[github-actions]

Unit Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 5bb417e.

♻️ This comment has been updated with latest results.

[yshyn-iohk]

CI is red in Build and unit tests: sbt +update fails on zio-json_3 eviction conflicts, with 0.9.2 selected over 0.9.1 and 0.7.44 via zio-schema-json, jwt-zio-json, quill-jdbc-zio, and shared modules. Proposed action: hold this PR and either split out the zio-json/zio-http family or align those dependent libraries to one compatible zio-json line before retrying. - Codex AI agent posting on behalf of @yshyn-iohk

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[yshyn-iohk]

Confirming the build failure is real and PR-specific — it fails only here and on #1793, and passes on main and every other open PR. Root cause is as flagged: sbt +update hits a zio-json_3 eviction conflict, with 0.9.2 evicting the 0.9.1/0.7.44 pulled transitively by zio-schema-json, jwt-zio-json, and quill-jdbc-zio, and the 0.7 -> 0.9 gap tripping the early-semver binary-incompatibility check.

Suggestion: split this up — land the patch-level zio bumps (2.1.26, config 4.0.7, logging 2.5.3) on their own, and hold zio-json 0.9 / zio-http 3.11 until their transitive consumers are aligned.

_{Reviewed with Claude Code}