[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
com.github.bitfireAT:dav4jvm	2.1.3 → 5.0.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

bitfireAT/dav4jvm (com.github.bitfireAT:dav4jvm)

v5.0.0

Compare Source

• DavCalendar.calendarQuery() and DavCalendar.multiget() now accept additionalHeaders.
  Needed so that clients can send the CalDAV-Timezones request header (RFC 7809) on the REPORTs that return iCalendar data.
  Source-compatible, but binary-incompatible: callers must be recompiled.
• ResponseParser now keeps server-provided hrefs in exactly the percent-encoded form they were returned in
  (and so do Url.parent(), Url.withTrailingSlash() and Url.omitTrailingSlash()).
  Some servers (for instance Stalwart) only accept report hrefs that match their own href form exactly and
  would return 404 otherwise, causing members to be skipped silently.

v4.1.0

Compare Source

• Add BadGatewayException that is thrown for HTTP 502 responses.
  DAV Services are often hosted behind a reverse proxy that will respond with a HTTP 502 status code when the actual service is temporarily not available. In most cases clients want to treat this as a soft error and retry the request later.
• Add content-encoding and fix Depth for WebDAV-Push

v4.0.1

Compare Source

v4.0.0

Compare Source

API change: the old synchronous, non-suspending callback pattern (like MultiResponseCallback) has been
replaced by suspend functions and Flows (#​200).
Methods that process a WebDAV Multi-Status response (like propfind) now return a Flow instead of
calling a callback; other request methods are plain suspend functions.

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

[!NOTE]
This release aims to give the library more stability, and start to provide releases with a more predictable versioning scheme.
The library is now in a stable state, and we will follow semantic versioning from now on.

This version migrates away from OkHttp to Ktor as the underlying HTTP client.
This allows for better multiplatform support, and more flexibility in terms of configuration.

You are still free to use OkHttp as the underlying engine, but now with the freedom of using other engines as well.
The old OkHttp-based API is no longer available, and you will need to migrate your code to the new Ktor-based API.

Migration should be straightforward, as the API is very similar. The main difference is regarding the HttpClient setup. Other functions can just be moved from the okhttp package to the ktor package, and the rest of the code should work as before.
Some utility functions may be missing though, if already provided by Ktor, or not useful anymore.

v2.2.1

Compare Source

v2.2

Compare Source

v2.1.4

Compare Source

---

Configuration

📅 Schedule: (in timezone Europe/Berlin)

• Branch creation
  • Between 01:00 AM and 04:59 AM (* 1-4 * * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: app/build.gradle.kts

Command failed: ./gradlew -Dorg.gradle.jvmargs=-Xms512m -Xmx512m --console=plain --dependency-verification lenient -q --write-verification-metadata sha256,pgp dependencies

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* What went wrong:
A problem occurred configuring root project 'talk-android'.
> Could not resolve all artifacts for configuration 'classpath'.
   > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin:2.4.21.
     Required by:
         buildscript of root project 'talk-android'
      > Repository Gradle Central Plugin Repository is disabled due to earlier error below:
         > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugins-bom:2.4.21.
            > Could not get resource 'https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-gradle-plugins-bom/2.4.21/kotlin-gradle-plugins-bom-2.4.21.pom'.
               > Could not GET 'https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-gradle-plugins-bom/2.4.21/kotlin-gradle-plugins-bom-2.4.21.pom'.
                  > Received status code 429 from server: Too Many Requests
> There are 51 more failures with identical causes.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights from a Build Scan (powered by Develocity).
> Get more help at https://help.gradle.org.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
A problem occurred configuring root project 'talk-android'.
> Could not resolve all artifacts for configuration 'classpath'.
   > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin:2.4.21.
     Required by:
         buildscript of root project 'talk-android'
      > Repository Gradle Central Plugin Repository is disabled due to earlier error below:
         > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugins-bom:2.4.21.
            > Could not get resource 'https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-gradle-plugins-bom/2.4.21/kotlin-gradle-plugins-bom-2.4.21.pom'.
               > Could not GET 'https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-gradle-plugins-bom/2.4.21/kotlin-gradle-plugins-bom-2.4.21.pom'.
                  > Received status code 429 from server: Too Many Requests
> There are 51 more failures with identical causes.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights from a Build Scan (powered by Develocity).
> Get more help at https://help.gradle.org.
==============================================================================

BUILD FAILED in 18s