Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update all dependencies #93

Merged
merged 2 commits into from
Nov 7, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 21, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.google.firebase:firebase-bom 33.4.0 -> 33.5.1 age adoption passing confidence
io.github.pdvrieze.xmlutil:serialization 0.90.2 -> 0.90.3 age adoption passing confidence
io.github.pdvrieze.xmlutil:core 0.90.2 -> 0.90.3 age adoption passing confidence
io.ktor:ktor-serialization-kotlinx-json 3.0.0 -> 3.0.1 age adoption passing confidence
io.ktor:ktor-client-content-negotiation 3.0.0 -> 3.0.1 age adoption passing confidence
io.ktor:ktor-client-mock 3.0.0 -> 3.0.1 age adoption passing confidence
io.ktor:ktor-client-okhttp 3.0.0 -> 3.0.1 age adoption passing confidence
io.ktor:ktor-client-core 3.0.0 -> 3.0.1 age adoption passing confidence
io.coil-kt.coil3:coil-test 3.0.0-rc01 -> 3.0.1 age adoption passing confidence
io.coil-kt.coil3:coil-network-ktor3 3.0.0-rc01 -> 3.0.1 age adoption passing confidence
io.coil-kt.coil3:coil-compose 3.0.0-rc01 -> 3.0.1 age adoption passing confidence
io.coil-kt.coil3:coil 3.0.0-rc01 -> 3.0.1 age adoption passing confidence
androidx.work:work-testing (source) 2.9.1 -> 2.10.0 age adoption passing confidence
androidx.work:work-runtime-ktx (source) 2.9.1 -> 2.10.0 age adoption passing confidence
androidx.compose:compose-bom 2024.10.00 -> 2024.10.01 age adoption passing confidence
androidx.lifecycle:lifecycle-runtime-compose (source) 2.8.6 -> 2.8.7 age adoption passing confidence
androidx.lifecycle:lifecycle-runtime-ktx (source) 2.8.6 -> 2.8.7 age adoption passing confidence
androidx.annotation:annotation (source) 1.9.0 -> 1.9.1 age adoption passing confidence
io.github.takahirom.roborazzi 1.29.0 -> 1.32.1 age adoption passing confidence
io.github.takahirom.roborazzi:roborazzi-junit-rule 1.29.0 -> 1.32.1 age adoption passing confidence
io.github.takahirom.roborazzi:roborazzi-compose 1.29.0 -> 1.32.1 age adoption passing confidence
io.github.takahirom.roborazzi:roborazzi 1.29.0 -> 1.32.1 age adoption passing confidence
androidx.core:core-ktx (source) 1.13.1 -> 1.15.0 age adoption passing confidence
com.android.test (source) 8.6.1 -> 8.7.2 age adoption passing confidence
com.android.library (source) 8.6.1 -> 8.7.2 age adoption passing confidence
com.android.application (source) 8.6.1 -> 8.7.2 age adoption passing confidence
com.android.tools.build:gradle (source) 8.6.1 -> 8.7.2 age adoption passing confidence

Warning

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


Release Notes

pdvrieze/xmlutil (io.github.pdvrieze.xmlutil:serialization)

v0.90.3

Changes:

  • In pedantic mode check that xml/xmlns are not used as names (they
    are always invalid). Note that namespaces can be specified using
    @XmlSerialName (for tags) and @XmlNamespaceDeclSpec (for
    additional names).
  • The cache to use can now be configured. By default it uses the
    threadLocal version, but the thread unsafe default is also available,
    as is the FormatCache.Dummy cache that does no caching.
    Fixes:
  • Fix support for multiple namespaces inside a single tag (QNameMap)
    as reported in #​249.
  • Use threadlocals for caching document structures by default. This should avoid
    multithreading issues when reusing the format (recommended for speed)
ktorio/ktor (io.ktor:ktor-serialization-kotlinx-json)

v3.0.1

Compare Source

Published 29 October 2024

Bugfixes
  • Remove space from the default client user agent (KTOR-7655)
  • Url.segments throws on URLs with root path (KTOR-7625)
  • Digest Auth does not implement nc parameter correctly according to RFC 7616 (KTOR-4318)
  • about:blank URL should be parsed correctly as about:blank (KTOR-7410)
  • ByteReadChannel.{readShort/readInt/readLong} could lead to CPU-bound indefinite loop since 3.0.0 (KTOR-7571)
  • CIO: Requests face connection timeouts when executed on the Android main dispatcher (KTOR-6803)
  • receiveMultipart fails with "IOException: Failed to parse multipart" when content-type is capitalized (KTOR-7596)
Improvements
  • WebSockets logging: The plugin calls toString() unnecessarily on transformed response body (KTOR-7623)
  • INFO log message with all server interceptors on server startup (KTOR-7326)
  • Digest auth: username and cnonce parameters aren't surrounded with quotes (KTOR-7561)
  • ContentType.fromFilePath for newer file formats HEIC, AVIF, HEIF (KTOR-7536)
  • Support missing native targets in ktor-serialization-kotlinx-xml (KTOR-7583)
coil-kt/coil (io.coil-kt.coil3:coil-test)

v3.0.1

Compare Source

  • Fix crash when calling Image.toBitmap with a hardware bitmap-backed BitmapImage.
  • Fix AsyncImageModelEqualityDelegate.Default comparing equality incorrectly for non-ImageRequest models.

v3.0.0

Compare Source

Coil 3.0.0 is the next major release of Coil with full support for Compose Multiplatform.

For the full list of improvements and important changes in 3.0.0, check out the upgrade guide.

Changes since 3.0.0-rc02:

  • Remove remaining deprecated methods.

v3.0.0-rc02

Compare Source

For the full list of improvements and important changes in 3.x, check out the upgrade guide. Changes since 3.0.0-rc01:

  • Add BlackholeDecoder. This simplifies disk-cache only preloading.
  • Add remember functions for ConstraintsSizeResolver and DrawScopeSizeResolver.
  • Remove EqualityDelegate as a parameter to AsyncImage. Instead, it should be set through LocalAsyncImageModelEqualityDelegate.
  • Fix AsyncImage not rendering when parent composable uses IntrinsicSize.
  • Fix AsyncImage filling the available constraints when AsyncImagePainter has no child painter.
  • Fix rememberAsyncImagePainter recomposing infinitely when its state is observed due to EqualityDelegate being ignored.
  • Fix parsing File/Path paths with special characters.
  • Fix using custom FileSystem implementations with VideoFrameDecoder.
  • Update Ktor to 3.0.0.
  • Update androidx.annotation to 1.9.0.
takahirom/roborazzi (io.github.takahirom.roborazzi)

v1.32.1

Compare Source

Experimental WebP support and other image formats

Now, you can set roborazzi.record.image.extension to webp in your gradle.properties file to generate WebP images.
To enable WebP support, add testImplementation("io.github.darkxanter:webp-imageio:0.3.3") to your build.gradle.kts file.

roborazzi.record.image.extension=webp

WebP is a lossy image format by default, which can make managing image differences challenging. To address this, we provide a lossless WebP image feature.

onView(ViewMatchers.withId(R.id.textview_first))
  .captureRoboImage(
    roborazziOptions = RoborazziOptions(
      recordOptions = RoborazziOptions.RecordOptions(
        imageIoFormat = LosslessWebPImageIoFormat(),
      ),
    )
  )

You can also use other image formats by implementing your own AwtImageWriter and AwtImageLoader.

data class JvmImageIoFormat(
  val awtImageWriter: AwtImageWriter,
  val awtImageLoader: AwtImageLoader
) : ImageIoFormat

Thank you, @​ArcaNO93, for providing this suggestion and the code review!

Adjustments to AI-Powered Image Assertion

In version 1.30.0, we introduced Roborazzi AI-Powered Image Assertion.
We made some adjustments to the AI-Powered Image Assertion

  • The OpenAiAiAssertionModel, which utilizes OpenAI APIs, previously lacked a timeout specification, leading to frequent timeout issues. We have now implemented a customizable timeout setting.
  • The provideRoborazziContext().option was marked as InternalRoborazziApi despite being documented in the README. We have now changed it to ExperimentalRoborazzi API.

Changes from 1.32.0

API Key Masking in Logs for OpenAiAiAssertionModel
For users enabling logging through OpenAiAiAssertionModel.loggingEnabled, API keys in log outputs are now masked to improve security. Previously, API keys could appear in logs, which could unintentionally expose them, especially in test reports. With this update, sensitive data is automatically masked, helping users avoid accidental exposure.

What's Changed

Full Changelog: takahirom/roborazzi@1.31.0...1.32.1

v1.32.0

Compare Source

Experimental WebP support and other image formats

Now, you can set roborazzi.record.image.extension to webp in your gradle.properties file to generate WebP images.
To enable WebP support, add testImplementation("io.github.darkxanter:webp-imageio:0.3.3") to your build.gradle.kts file.

roborazzi.record.image.extension=webp

WebP is a lossy image format by default, which can make managing image differences challenging. To address this, we provide a lossless WebP image feature.

onView(ViewMatchers.withId(R.id.textview_first))
  .captureRoboImage(
    roborazziOptions = RoborazziOptions(
      recordOptions = RoborazziOptions.RecordOptions(
        imageIoFormat = LosslessWebPImageIoFormat(),
      ),
    )
  )

You can also use other image formats by implementing your own AwtImageWriter and AwtImageLoader.

data class JvmImageIoFormat(
  val awtImageWriter: AwtImageWriter,
  val awtImageLoader: AwtImageLoader
) : ImageIoFormat

Thank you, @​ArcaNO93, for providing this suggestion and the code review!

Adjustments to AI-Powered Image Assertion

In version 1.30.0, we introduced Roborazzi AI-Powered Image Assertion.
We made some adjustments to the AI-Powered Image Assertion

  • The OpenAiAiAssertionModel, which utilizes OpenAI APIs, previously lacked a timeout specification, leading to frequent timeout issues. We have now implemented a customizable timeout setting.
  • The provideRoborazziContext().option was marked as InternalRoborazziApi despite being documented in the README. We have now changed it to ExperimentalRoborazzi API.
What's Changed

Full Changelog: takahirom/roborazzi@1.31.0...1.32.0

v1.31.0

Compare Source

Added Experimental Support for Cleaning Up Old Screenshots

This release introduces the roborazzi.cleanupOldScreenshots=true option in gradle.properties, allowing users to automatically remove outdated screenshots. By default, this is set to false to prevent accidental deletions when running filtered tests. Please note that enabling this option may result in unintended deletions when running filtered tests. You can use -Proborazzi.cleanupOldScreenshots=true for CI configurations to clean up screenshots only in CI runs without affecting local settings.
This cleanup implementation may affect the cache mechanism. We have some integration tests in place, but if you notice any issues, please let us know.
Thank you, @​JackEblan, for suggesting the cleanup feature!

Improve AI Assertion Error Message

In the previous release, we introduced Roborazzi AI-Powered Image Assertion.
When an AI assertion fails, it’s important to review the screenshots to understand what went wrong with the images. Therefore, I enhanced the error message to include the file paths of the images.

image

What's Changed

Full Changelog: takahirom/roborazzi@1.30.1...1.31.0

v1.30.1

Compare Source

Roborazzi AI-Powered Image Assertion 🤖 ✨

Roborazzi introduces an experimental AI-powered image assertion feature to simplify and scale the process of verifying screenshot test content. This feature helps automate tedious visual checks by comparing images based on customizable AI prompts, utilizing either the Gemini API or OpenAI API. It only activates when images differ, conserving resources. Additionally, manual AI assertion is available, allowing users to leverage local language models without external dependencies.
We don't include Gemini or OpenAI dependencies in the roborazzi module. To use these models, you can add either roborazzi-ai-gemini or roborazzi-ai-openai as dependencies.

  onView(ViewMatchers.isRoot())
    .captureRoboImage(
      roborazziOptions = provideRoborazziContext().options.addedAiAssertion(
        assertionPrompt = "The screen should have a PREVIOUS button",
      )
   )

For more information, please check out this documentation page:
https://takahirom.github.io/roborazzi/ai-powered-image-assertion.html

Roborazzi Compose Preview Support now supports the device parameter@Preview(device = "") 📱

Roborazzi Compose Preview Support uses ComposablePreviewScanner and ComposablePreviewScanner now supports parsing device parameter. It is introduced to Compose Preview Support. Thank you, @​sergio-sastre, for developing this adapter and integrating it with Roborazzi.
If you are using Roborazzi Compose Preview Support with device parameters, you need to update your ComposablePreviewScanner to version 0.4.0.

Remove Context Receiver from roborazzi-desktop ♻️

The Context Receiver in Kotlin is now deprecated, so we need to remove it. The context(DesktopComposeUiTest) requirement existed because the file compose/ui/ui-test/src/skikoMain/kotlin/androidx/compose/ui/test/SkikoImageHelpers.kt was previously unavailable, necessitating the use of DesktopComposeUiTest. Now that SkikoImageHelpers is available, we can eliminate the context(DesktopComposeUiTest) requirement.

This functionality was introduced in the Compose Multiplatform core repository (commit 1664fba: JetBrains/compose-multiplatform-core@1664fba) and has been supported since Compose Multiplatform version 1.5.12 (https://github.com/JetBrains/compose-multiplatform-core/releases/tag/v1.5.12).
Please note that this may be a breaking change if you are using Compose Multiplatform version 1.5.12 or earlier.

Changes from 1.30.0
  • Breaking changes to 1.30.0:
    Renamed parameter assertPrompt to assertionPrompt.

  • Use max_tokens instead of max_completion_tokens for the OpenAI API:
    Although max_tokens has been deprecated, we still need to use it in certain environments.

What's Changed
New Contributors

Full Changelog: takahirom/roborazzi@1.29.0...1.30.0
Full Changelog: takahirom/roborazzi@1.30.0...1.30.1

v1.30.0

Compare Source

Please refer to version 1.30.1


Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate renovate bot changed the title chore(deps): update all dependencies to v8.7.1 fix(deps): update all dependencies Oct 21, 2024
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from 84ec2d9 to ad0eab5 Compare October 29, 2024 21:29
@renovate renovate bot force-pushed the renovate/all branch 7 times, most recently from 5d3f78a to 8715153 Compare November 5, 2024 11:50
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from 2397ae2 to c832980 Compare November 7, 2024 10:36
Copy link
Contributor Author

renovate bot commented Nov 7, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@mr3y-the-programmer mr3y-the-programmer merged commit 6be4299 into main Nov 7, 2024
2 of 3 checks passed
@mr3y-the-programmer mr3y-the-programmer deleted the renovate/all branch November 7, 2024 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant