Update all dependencies - autoclosed #2486
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate-bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
2e1ebf5 to
e3121ce
Compare
renovate-bot
force-pushed
the
renovate/all
branch
from
e3121ce to
a85c19a
Compare
renovate-bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.11.1->8.126.6.1->6.6.21.36.0->1.39.01.36.0->1.39.01.36.0->1.39.01.36.0->1.39.01.36.0->1.39.01.36.0->1.39.04.29.1->4.29.24.29.1->4.29.22.53.1->2.542.53.1->2.542.53.1->2.542.53.1->2.541.9.20->2.0.01.9.20->2.0.02.6.0->2.6.11.5.0->1.5.11.5.0->1.5.11.5.0->1.5.11.5.0->1.5.11.5.0->1.5.11.5.0->1.5.11.5.0->1.5.11.5.0->1.5.11.5.0->1.5.11.5.0->1.5.11.5.0->1.5.1Release Notes
gradle/gradle (gradle)
v8.12Compare Source
airbnb/lottie-android (com.airbnb.android:lottie-compose)
v6.6.2Bugs Fixed
takahirom/roborazzi (io.github.takahirom.roborazzi)
v1.39.0Compare Source
Bug Fixes
Diff screenshots are now as large as the largest of the two compared screenshots
Previously, when the size of a screenshot changed (e.g., became smaller), the image diff would not appear because it was based on the minimum size of each screenshot. This has been fixed so that the diff is now based on the largest of the two compared screenshots. Thank you for reporting this issue, @outadoc!
Report HTML's image order is now deterministic
The image order in the HTML report used to be random. Thanks to @mannodermaus, it is now sorted by name.
OpenAiAiAssertionModel is now Gemini compatible
Gemini has a compatibility mode with the OpenAI API (https://ai.google.dev/gemini-api/docs/openai). By using
https://generativelanguage.googleapis.com/v1beta/openai/as the base URL, we can essentially use Gemini. However, some properties are different, so we had to modify the OpenAiAiAssertionModel to be compatible with Gemini.I'm currently developing another library called Arbigent, an AI agent testing framework. I'm planning to add an AI image assertion feature using Roborazzi's AI-Powered Image Assertion, and I needed this compatibility for that. This isn't directly related to this project, but if you're interested in testing, check it out: https://github.com/takahirom/arbigent
What's Changed
b96c8e6by @renovate in https://github.com/takahirom/roborazzi/pull/561Full Changelog: takahirom/roborazzi@1.38.0...1.39.0
v1.38.0Compare Source
Bugfix
Fix: Bug preventing the revival of deleted screenshot images
Thanks to @pedromfmachado's contribution, we've addressed a bug where deleted screenshot test images would be erroneously revived. Previously, when screenshot tests were removed and their corresponding images deleted from the output directory, running the
recordtask again would cause the Roborazzi Gradle task to recreate the removed images. While this could be temporarily resolved withroborazzi.cleanupOldScreenshots=true, that approach was undesirable as it would also remove images when test filters were used. This was a complex issue to solve, and we extend our gratitude to @pedromfmachado for the fix.Fix: Made screenshot dump deterministic
We have a dump feature that allows us to check the properties or hierarchy of views or composables in an image. We sorted the properties to ensure a deterministic output. Thanks to @siarhei-luskanau for this contribution.
New Feature
Feature: Added
RoborazziComposeActivityThemeOptionPreviously, changing the theme of
RoborazziTransparentActivitywas not possible. We have now deprecatedRoborazziTransparentActivityand renamed it toRoborazziActivity. Additionally, we addedRoborazziComposeActivityThemeOptionto enable changing the Activity's theme. Thank you again, @pedromfmachado, for this feature.You can now change the Activity theme like this:
What's Changed
New Contributors
Full Changelog: takahirom/roborazzi@1.37.0...1.38.0
v1.37.0Compare Source
Bug Fixes and Workarounds
Compose AlertDialog Support
Support for capturing Alert Dialogs has been fixed, ensuring correct screenshot display.
captureScreenRoboImage(), which merges all windows, is now used only when multiple windows are present. Thanks to @ashughes for reporting this and to @mhidaka and @hiroaki404 for bringing it to my attention at a Japan Android testing event.Workaround for Overlap Handling for SDK 35 Compose Screenshots
Problem
When updating to SDK 35 and using the default theme, the ActionBar is included in screenshots, leading to overlap when using
createComposeRule(). This occurs becausecreateComposeRule()uses the default theme by default. Thank you for letting me know about this, @keyboardsurfer!I have filed an issue for this: https://issuetracker.google.com/issues/383368165
Why this happens
SDK 35 enforces edge-to-edge display, which means it does not provide automatic padding for the ActionBar.
How Roborazzi currently workarounds this
Roborazzi now automatically hides the ActionBar when taking screenshots on SDK 35 and higher. This functions similarly to
view.getActivity()?.actionBar?.hide(). However, this workaround may cause performance issues and should not be relied upon. Roborazzi outputs warning logs with alternative suggestions. Thank you to @sergio-sastre for advising on this workaround!If you need to include the ActionBar in screenshots, Roborazzi provides a flag,
roborazzi.compose.actionbar.overlap.fix=false, that can be added to yourgradle.propertiesfile.What should we do?
A permanent solution will likely require changes from Google. In the meantime, adding
<application android:theme="@​style/android:Theme.Material.Light.NoActionBar" />to the module'ssrc/test/AndroidManifest.xmlfile changes the Activity's default theme and resolves the issue. Thank you to @mattinger for finding this!https://github.com/takahirom/roborazzi/issues/598#issuecomment-2533372700
Stabilized Output for Dump Screenshots
Thanks to @siarhei-luskanau for contributing an improvement that reduces unnecessary diffs for the Roborazzi dump feature.
New Features
Add
inspectionMode()for Compose PreviewsThanks to @YusukeMoriJapan's contribution,
inspectionMode()is now available inRoborazziComposeOptions. This is particularly useful when working with libraries that have specific preview implementations. This mode is off by default to maintain high fidelity.Here's how to enable it:
captureRoboImage( roborazziComposeOptions = RoborazziComposeOptions { inspectionMode(true) } ) { ... }What's Changed
New Contributors
Full Changelog: takahirom/roborazzi@1.36.0...1.37.0
Kotlin/dokka (org.jetbrains.dokka:dokka-gradle-plugin)
v2.0.0: 2.0.0Dokka 2.0.0 focuses on simplifying configuration and preparing for support of future Kotlin language features. Key highlights include:
More details about each of the changes below. See Dokka 2.0.0 milestone for the list of all changes.
Dokka's Gradle plugin v2 based on Dokkatoo
Dokka 2.0.0 introduces significant improvements to Dokka Gradle plugin, aligning more closely with Gradle best practices:
Changes from Dokka 2.0.0-Beta
dokkaPublicationDirectorytobasePublicationsDirectory(https://github.com/Kotlin/dokka/pull/3876)dokkaModuleDirectory, and mark as internal (https://github.com/Kotlin/dokka/pull/3880)dokkaGenerateondokkaGenerateModule*(https://github.com/Kotlin/dokka/pull/3920)Dokka's K2 analysis
Dokka 2.0.0 introduces K2 analysis, which is currently in an experimental stage. Dokka's K2 analysis leverages Kotlin's K2 compiler frontend for analysing code and uses the same shared Analysis API, which is used in IntelliJ IDEA’s K2 mode. The output with K2 analysis should mostly match that of K1 analysis, but there may be minor differences. We are actively working towards stabilizing K2 analysis and are planning to enable K2 analysis by default in future.
To opt in to Dokka's K2 analysis, add the following flag to your project's
gradle.propertiesfile:org.jetbrains.dokka.experimental.tryK2=trueKnown limitations:
We would greatly value your feedback if you encounter any of these limitations.
Potential differences between the outputs of K1 and K2:
While the output of K2 analysis aims to align with K1, there are some differences to be aware of:
HTML format
Dokka 2.0.0 introduces some changes to HTML output. We updated the structure of some elements and classes, particularly in the navigation and sidebar, to improve accessibility and simplify maintenance. These changes only affect you if you previously customized Dokka styles.
navigation--innerandnavigation-title.versions-dropdownto make them more accessible.navigation-controls--homepageto improve consistency. For example, it’s now callednavigation-controls--btn_homepage.For more information, see the pull request.
The easiest way to update your current templates is to adjust the new templates to your needs.
Bugfixes
Other changes
Feedback
We would appreciate your feedback!
Full Changelog: Kotlin/dokka@v1.9.20...v2.0.0
androidx/media (androidx.media3:media3-ui)
v1.5.1Compare Source
This release includes the following changes since the
1.5.0 release:
codec timeout issues with this platform API
(#1641).
VBRIframe's table of contentsdoesn't cover all the MP3 data in a file
(#1904).
MediaCodecAdaptersupplied pixel aspect ratio valueswhen provided while processing
onOutputFormatChanged(#1371).
ReplacingCuesResolver.discardCuesBeforeTimeUswhere the cueactive at
timeUs(started before but not yet ended) was incorrectlydiscarded (#1939).
MediaMetadata(#1958).
Configuration
📅 Schedule: Branch creation - "* 0-3 * * *" (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.
This PR was generated by Mend Renovate. View the repository job log.