Update slf4j-backend, upickle to 4.0.13

[xerial-bot]

About this PR

📦 Updates

• com.softwaremill.sttp.client4:slf4j-backend
• com.softwaremill.sttp.client4:upickle

from 4.0.0-M16 to 4.0.13

📜 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'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.softwaremill.sttp.client4" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.softwaremill.sttp.client4" }
}]

^{labels: library-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1}

[gemini-code-assist]

Summary of Changes

Hello @xerial-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a routine dependency update for the sttp client library, specifically its slf4j-backend and upickle modules. The update moves from a milestone release (4.0.0-M16) to a stable version (4.0.13), aiming to incorporate the latest features, performance enhancements, and stability improvements provided by the library maintainers.

Highlights

• Dependency Update: The slf4j-backend and upickle components of the com.softwaremill.sttp.client4 library have been updated from version 4.0.0-M16 to 4.0.13.
• STTP Library Upgrade: This pull request upgrades the sttp client library to its latest stable version, 4.0.13, ensuring the project benefits from recent improvements and bug fixes.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the sttp dependency from a milestone release 4.0.0-M16 to the stable version 4.0.13. While this is a good update, I've raised a concern about potential binary incompatibilities with the sonatype-central-client-sttp-core dependency, which also relies on sttp. I've recommended verifying compatibility and potentially updating both dependencies together to prevent runtime issues.

[gemini-code-assist]

This update to sttp version 4.0.13 might cause issues. The project also depends on com.lumidion:sonatype-central-client-sttp-core:0.3.0 (via versions.sonatypeClient), which itself has a dependency on sttp.

If sonatype-central-client-sttp-core:0.3.0 was compiled against an older, binary-incompatible version of sttp (like the previous 4.0.0-M16), this update could lead to runtime errors such as NoSuchMethodError.

It is highly recommended to verify the sttp version compatibility of sonatype-central-client-sttp-core:0.3.0 or check if a newer version of sonatype-central-client should be used alongside this sttp update. Ideally, these related dependencies should be updated together to ensure compatibility.