chore(deps): bump androidxComposeMaterial3Adaptive from 1.0.1 to 1.1.0+dev1976

[dependabot]

Bumps androidxComposeMaterial3Adaptive from 1.0.1 to 1.1.0+dev1976.
Updates org.jetbrains.compose.material3.adaptive:adaptive from 1.0.1 to 1.1.0+dev1976

Changelog

Sourced from org.jetbrains.compose.material3.adaptive:adaptive's changelog.

1.8.0-alpha01 (November 2024)

Changes since 1.7.1

Highlights

iOS

• LocalUIViewController moved to the androidx.compose.ui.uikit module
• Update AccessibilitySyncOptions and remove AccessibilityDebugLogger from public API
• ComposeUIViewControllerDelegate marked as deprecated. Use parent view controller to override the methods of the UIViewController class
• Remove experimental flag from fun enableTraceOSLog()
• Remove obsolete Canvas Layers mode on iOS

Breaking Changes

Multiple Platforms

• Tests that relied on waitForIdle, awaitIdle or runOnIdle (whether explicit or implicit) executing delay-ed coroutines will no longer work correctly. To fix this advance the test time via mainClock manually, as needed For example, tests that previously did something like:

  var updateText by mutableStateOf(false)
  var text by mutableStateOf("0")
  setContent {
      LaunchedEffect(updateText) {
          if (updateText) {
              delay(1000)
              text = "1"
          }
      }
  }
  updateText = true
  waitForIdle()
  assertEquals("1", text)
  

  will need to add mainClock.advanceTimeBy(1000) after waitForIdle(), because waitForIdle no longer waits for the delay-ed coroutine to complete
• Tests that advance the test clock (via mainClock.advanceTimeBy) may see different behavior with regards to the amount and timing of recomposition, layout, drawing and effects
• runOnIdle will now execute action on the UI thread
• runOnIdle will no longer call waitForIdle after executing the action
• Advancing mainClock such that it doesn't reach the next frame, will no longer cause a recomposition

Desktop

• Deprecated/experimental Modifier.onExternalDrag has been removed - common Modifier.dragAndDropTarget API should be used instead

Features

Multiple Platforms

• Support configurable vertical text centering via LineHeightStyle.Alignment

... (truncated)

Commits

• See full diff in compare view

Updates org.jetbrains.compose.material3.adaptive:adaptive-layout from 1.0.1 to 1.1.0+dev1976

Changelog

Sourced from org.jetbrains.compose.material3.adaptive:adaptive-layout's changelog.

1.8.0-alpha01 (November 2024)

Changes since 1.7.1

Highlights

iOS

• LocalUIViewController moved to the androidx.compose.ui.uikit module
• Update AccessibilitySyncOptions and remove AccessibilityDebugLogger from public API
• ComposeUIViewControllerDelegate marked as deprecated. Use parent view controller to override the methods of the UIViewController class
• Remove experimental flag from fun enableTraceOSLog()
• Remove obsolete Canvas Layers mode on iOS

Breaking Changes

Multiple Platforms

• Tests that relied on waitForIdle, awaitIdle or runOnIdle (whether explicit or implicit) executing delay-ed coroutines will no longer work correctly. To fix this advance the test time via mainClock manually, as needed For example, tests that previously did something like:

  var updateText by mutableStateOf(false)
  var text by mutableStateOf("0")
  setContent {
      LaunchedEffect(updateText) {
          if (updateText) {
              delay(1000)
              text = "1"
          }
      }
  }
  updateText = true
  waitForIdle()
  assertEquals("1", text)
  

  will need to add mainClock.advanceTimeBy(1000) after waitForIdle(), because waitForIdle no longer waits for the delay-ed coroutine to complete
• Tests that advance the test clock (via mainClock.advanceTimeBy) may see different behavior with regards to the amount and timing of recomposition, layout, drawing and effects
• runOnIdle will now execute action on the UI thread
• runOnIdle will no longer call waitForIdle after executing the action
• Advancing mainClock such that it doesn't reach the next frame, will no longer cause a recomposition

Desktop

• Deprecated/experimental Modifier.onExternalDrag has been removed - common Modifier.dragAndDropTarget API should be used instead

Features

Multiple Platforms

• Support configurable vertical text centering via LineHeightStyle.Alignment

... (truncated)

Commits

• See full diff in compare view

Updates org.jetbrains.compose.material3.adaptive:adaptive-navigation from 1.0.1 to 1.1.0+dev1976

Changelog

Sourced from org.jetbrains.compose.material3.adaptive:adaptive-navigation's changelog.

1.8.0-alpha01 (November 2024)

Changes since 1.7.1

Highlights

iOS

• LocalUIViewController moved to the androidx.compose.ui.uikit module
• Update AccessibilitySyncOptions and remove AccessibilityDebugLogger from public API
• ComposeUIViewControllerDelegate marked as deprecated. Use parent view controller to override the methods of the UIViewController class
• Remove experimental flag from fun enableTraceOSLog()
• Remove obsolete Canvas Layers mode on iOS

Breaking Changes

Multiple Platforms

• Tests that relied on waitForIdle, awaitIdle or runOnIdle (whether explicit or implicit) executing delay-ed coroutines will no longer work correctly. To fix this advance the test time via mainClock manually, as needed For example, tests that previously did something like:

  var updateText by mutableStateOf(false)
  var text by mutableStateOf("0")
  setContent {
      LaunchedEffect(updateText) {
          if (updateText) {
              delay(1000)
              text = "1"
          }
      }
  }
  updateText = true
  waitForIdle()
  assertEquals("1", text)
  

  will need to add mainClock.advanceTimeBy(1000) after waitForIdle(), because waitForIdle no longer waits for the delay-ed coroutine to complete
• Tests that advance the test clock (via mainClock.advanceTimeBy) may see different behavior with regards to the amount and timing of recomposition, layout, drawing and effects
• runOnIdle will now execute action on the UI thread
• runOnIdle will no longer call waitForIdle after executing the action
• Advancing mainClock such that it doesn't reach the next frame, will no longer cause a recomposition

Desktop

• Deprecated/experimental Modifier.onExternalDrag has been removed - common Modifier.dragAndDropTarget API should be used instead

Features

Multiple Platforms

• Support configurable vertical text centering via LineHeightStyle.Alignment

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

The following labels could not be found: version update.

[mshdabiola]

@dependabot ignore this minor version

[dependabot]

OK, I won't notify you about version 1.1.x again, unless you re-open this PR.