fix(deps): update dependency com.github.loki4j:loki-logback-appender to v1.6.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.github.loki4j:loki-logback-appender	1.5.2 -> 1.6.0

---

Release Notes

loki4j/loki-logback-appender (com.github.loki4j:loki-logback-appender)

v1.6.0

Compare Source

Version 1.6.0 contains several new features and improvements. The most notable one is probably structured metadata support. There are some breaking changes in compatibility matrix, protobuf support, and some format settings. Please check the Migration guide for the details.

New features

#​233 Key-value pairs support in JSON layout
#​236 Upgrade proto file from the upstream
#​237 Drop Java 8 support
#​238 Upgrade Logback to 1.4.x
#​239 Report time to Loki with nanosecond precision
#​259 Structured metadata support
#​267 Ignore whitespace in label and structured metadata patterns
#​271 Drop sorting records by time
#​279 Json message layer: support of writing arbitrary objects

Bug fixes

#​243 Loki appender didn't retry on HttpConnectTimeoutException

Refactoring

#​265 Key-value pairs extraction rework

Misc

#​229 Switch integration test from Loki 2.9.1 to Loki 3.0.0
#​234 Upgrade Github actions
#​235 Fix Grafana Cloud test
#​248 Performance tests for JsonLayout fix options
#​254 Fix published licence URL
#​260 Switch integration test from Loki 3.0.0 to Loki 3.2.0
#​261 Add Java 22 to compatibility test
#​268 Dependencies upgraded
#​276 Upgrade protobuf dependency to 4.29
#​277 Switch integration test from Loki 3.2.0 to Loki 3.3.1
#​278 Switch compatibility test from Java 22 to Java 23

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[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

[github-actions]

Qodana Community for JVM

102 new problems were found

Inspection name	Severity	Problems
Unchecked warning	🔶 Warning	36
@NotNull/@Nullable problems	🔶 Warning	30
'equals()' method which does not check class of parameter	🔶 Warning	21
Nullability and data flow problems	🔶 Warning	3
Field can be local	🔶 Warning	3
Declaration has problems in Javadoc references	🔶 Warning	2
AutoCloseable used without 'try'-with-resources	🔶 Warning	1
Class is exposed outside of its visibility scope	🔶 Warning	1
Default annotation parameter value	🔶 Warning	1
Javadoc declaration problems	🔶 Warning	1
Mismatched query and update of collection	🔶 Warning	1
Optional.get() is called without isPresent() check	🔶 Warning	1
Commented out code	◽️ Notice	1

☁️ View the detailed Qodana report

Contact Qodana team

Contact us at [email protected]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions