Repository navigation
fix(deps): update dependency me.mmckenna.dejavu:dejavu to v0.5.0 - #1477
Merged
Merged
Conversation
This file contains hidden or 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
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:
0.3.1→0.5.0Release Notes
himattm/dejavu (me.mmckenna.dejavu:dejavu)
v0.5.0Changed
DejaVu keeps independent version numbers and the Android Compose 1.11 support floor.
Retire the redundant intermediate 2026.06.00 checkpoint without moving the support floor.
The published AAR requires consumers to use compile SDK 37. Retaining Android Compose 1.11
requires an enforced BOM so the transitive 1.12 baseline does not win resolution.
pressedAPI with separate 1.11 and 1.12test sources. Both retain the same deliberately inefficient and stable fixture behavior.
Skiko bundling check. The library continues to publish Wasm KLIB artifacts.
Added
hasPendingWorkandrunWithoutImplicitWaitAPIs.These new methods require Compose 1.12; existing rule methods remain covered on Compose 1.11.
SideEffect, shrinkingvararg effect keys, shrinking
rememberkeys, frame assertions usingrunWithoutImplicitWait,and nested movable content under the LinkBuffer composer.
quiet, proving DejaVu counts every recomposition and rejects an incorrect stability budget.
Unkeyed
SideEffectremains the independent recomposition-count oracle.complete core suite and the original 20 experimental tests; 1.12 adds the six new regressions.
the KMP baseline. Release checks now reject empty, failing, or skipped JUnit reports.
Fixed
setTrackedContent.Previously, enabling the Android tracking rule before a KMP helper test in the same process
could hide the helper's subcomposition and report an unmapped tag. A dedicated Android
regression and the packaged consumer suite cover both harnesses together.
a subsequent Android rule keeps tracking. The regression checks the full rule/helper/rule path.
after a previous test disabled tracking. The setup regression verifies the first update against
an independent
SideEffectcount.v0.4.0Changed
assertions (
assertRecompositions(atLeast = …/atMost = …),atLeast = 0) in thedejavupattern tests and the
demoinstrumented tests with exact assertions — either a pinned budget(
exactly = N/assertStable()) or, indejavu/commonTest, aSideEffect-ground-truthequality (
exactly = GroundTruth.delta(tag)for single-instance / distinct-call-site nodes, andDejavuTracer.getRecompositionCount(fn) == GroundTruth.delta(fn)at the function level forkeyless-loop / multi-tag composables whose per-instance counts only resolve on Android). This
proves the tracer's counts are accurate, not merely non-zero. Added a shared
GroundTruthtest helper (
record/snapshotBaseline/delta) mirroring thecompose-experimentalpattern.Two narrow classes stay directional by design: the assertion-API coverage tests
(
AssertionApiPatternTest/ demoAssertionApiTest, which exerciseatLeast/atMost/range)and continuously-running animation / scroll-frame counts whose exact value is a moving target.
Added
.claude/skills/to help AI agents adopt Dejavu, author tests, triage failures, and run an iterative recomposition-optimization loop:dejavu-onboarding— adds Dejavu to a project from scratch (gradle dependency, firstModifier.testTag, smallest passing test).dejavu-test-writer— authors Compose UI recomposition tests using Dejavu's APIs.dejavu-error-triage— one-shot diagnosis of a singleUnexpectedRecompositionsErrorblock.dejavu-perf-loop— closed-loop optimization using Dejavu as the validator.dejavu) installable via/plugin marketplace add mttmcknn/dejavu+/plugin install dejavu@dejavu. Plugin manifest at.claude-plugin/plugin.json, marketplace at.claude-plugin/marketplace.json, withskills/symlinked into.claude/skills/for a single source of truth.compose-experimentalmodule (a staging area for experimental-API recomposition coverage) with tests for Compose 1.11's new APIs, running on JVM, iOS, Wasm, and Android instrumented: experimentalGrid, experimentalFlexBox, the experimental LinkBuffer composer runtime path (ComposeRuntimeFlags.isLinkBufferComposerEnabled),movableContentOf,derivedMediaQuery/mediaQuery(adaptive breakpoints), and the Styles API (androidx.compose.foundation.style).ComposeUiTest.resetRecompositionCounts()for KMP recomposition tests — resets recomposition counts mid-test while preserving composition history.test.shrelease check andRELEASING.mdchecklist that pin one ComposeMultiplatform/BOM baseline per Dejavu release while retaining older supported BOM checkpoints.
Compatibility
in the 1.10 BOM line. Compose 1.10 remains supported by Dejavu 0.3.1.
androidx.compose.ui.test.v2.runComposeUiTest,androidx.compose.ui.test.junit4.v2.createAndroidComposeRule), which default toStandardTestDispatcher(v1 usedUnconfinedTestDispatcher). This completes the testing-v2 half of #63. Validated that recomposition counts are unchanged on JVM under the new dispatcher — no rebaselining was required.iosX64from supported targets because Compose Multiplatform 1.11 no longer supports Apple x64 targets. iOS coverage remains viaiosArm64(compile) andiosSimulatorArm64(tests).movableContentOfregression tests into the cross-platformcompose-experimentalcommon test set (JVM, iOS, Wasm) alongside Android instrumented coverage.2026.06.00, and the 2026.06.01 release baseline. Each Android checkpoint runs both the legacy
UI suite and the new Compose 1.11 composable/runtime regressions.
release suite and exact verified commit can replace repeated hosted CI checks, conserving CI budget.
Fixed
in a hash set; hashing its changing contents caused lazy-layout registration to crash on iOS and
Wasm. All eight lazy-row/grid accuracy tests now run on every target (#21).
TestResultfromrunRecompositionTrackingUiTestand keep trackingactive across suspensions. The block now accepts suspending calls, matching Compose testing v2.
Return the helper result directly from each Wasm test; recompile test binaries after upgrading.
asynchronous UI test. The previous helper read an empty result before the test completed (#22).
-PcomposeBomVersionuse an enforced platform during compatibility checks. This preventsCompose Multiplatform's newer transitive Android artifacts from silently replacing an older BOM
and making a compatibility job test the wrong runtime.
CommonTagMappingin the per-frame fallback pass after their initialmapping, so their recompositions continue to be detected. Android's primary tooling pass now
hands off its exact mapped-tag set instead of treating every previously known tag as handled.
SideEffectground-truth test counters used across UI and instrumentation threads.produceState/snapshotFlowAndroid regressions compare Dejavu with aSideEffectground truth, and remove the random reset setup that could flake 1 in 720 runs.Removed
-PexcludeCompositionObserver/src/observerAndroidsplit);CompositionObserversupport is now unconditional.Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR has been generated by Mend Renovate CLI.