Update spice-client-okhttp to 0.3.0

[darkfrog26]

About this PR

📦 Updates com.outr:spice-client-okhttp from 0.2.0 to 0.3.0

📜 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.outr", artifactId = "spice-client-okhttp" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.outr", artifactId = "spice-client-okhttp" }
}]

^{labels: library-update, early-semver-major, semver-spec-minor, version-scheme:semver-spec, commit-count:1}

Summary by CodeRabbit

• New Features

  • Updated Slack and Logstash dependencies for improved performance and compatibility.

• Refactor

  • Upgraded core library version to enhance system stability and feature set.

[coderabbitai]

Walkthrough

The recent update in the project's build.sbt file marks an upgrade of the spiceVersion from "0.2.0" to "0.3.0". This version bump is likely to bring in new features or fixes from the Spice library, which is used by the Slack and Logstash integrations within the project.

Changes

File(s)	Summary
build.sbt	Updated spiceVersion from "0.2.0" to "0.3.0".

🐇✨
A hop of version, a leap in code,
From 0.2.0 to 0.3.0 on the road.
May this small change, with its subtle might,
Bring bugs to heel and features to light. 🌟🚀

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ?

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• You can reply to a review comment made by CodeRabbit.
• You can tag CodeRabbit on specific lines of code or files in the PR by tagging @coderabbitai in a comment.
• You can tag @coderabbitai in a PR comment and ask one-off questions about the PR and the codebase. Use quoted replies to pass the context for follow-up questions.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 2dd0c25 and 52937b0.

Files selected for processing (1)

• build.sbt (1 hunks)

Additional comments: 1

build.sbt (1)

• 64-64: The update of the spiceVersion variable to "0.3.0" is correctly applied and is consistent with the PR's objective. Ensure that the new version does not introduce any breaking changes or require additional modifications to the project by reviewing the release notes and version diff provided in the PR description.