chore(deps): bump compose-destinations from 1.9.40-beta to 1.9.53

[dependabot]

Bumps compose-destinations from 1.9.40-beta to 1.9.53.
Updates io.github.raamcosta.compose-destinations:animations-core from 1.9.40-beta to 1.9.53

Release notes

Sourced from io.github.raamcosta.compose-destinations:animations-core's releases.

1.9.53

Versions update

• Compose 1.5.1
• Kotlin 1.9.10
• Jetpack Compose Navigation 2.7.2

Full Changelog: raamcosta/compose-destinations@1.9.52...1.9.53

1.9.51

• Dependencies updates

1.9.50 No longer beta! 🙌 No more accompanist-navigation! 🎉

Removed accompanist navigation since animations were imported to official compose navigation! 🎉

Because of this, some minor changes had to be made:

• DestinationStyleAnimated -> DestinationStyle.Animated
• rememberAnimatedNavHost -> rememberNavHost
• rememberAnimatedNavHostEngine -> rememberNavHostEngine (unless you are using bottom sheet destinations, in which case you still need to use rememberAnimatedNavHostEngine)
• ExperimentalAnimationApi removed on most APIs
• If you were not using DestinationsNavHost:
  • AnimatedNavHost -> NavHost
  • animatedComposable -> composable
• You no longer need animations-core unless you are using BottomSheet destinations (which still is using accompanist material under the hood)
• If you do still use animations-core, even if you don't need BottomSheet, it's totally fine, using rememberAnimatedNavHostEngine will just internally call rememberNavHostEngine.

No beta suffix? 🤔

Yes, that's right, there were a lot of insecurities hiding behind that "-beta" suffixed on all the lib's versions. The truth is that API changes might happen but each version is stable for production. This is especially annoying because some developers have company policies that state they cannot use this library because of this. So from now on, if big changes happen I will create alpha, beta, rc releases (not necessarily all three, as it seems quite unnecessary most of the time) related to that specific version, basically following practices that you might be used to with other jetpack libraries and such.

Thanks for being with me through this time, Compose Destinations is just getting started! Look forward to v2 which I honestly think will be great!

1.9.42-beta

Fixes

• Fixed #415 - issue that was happening if you were not using animations core.

Full Changelog: raamcosta/compose-destinations@1.9.41-beta...1.9.42-beta

Commits

• 86b5af3 versions update
• 81fc817 versions update
• e2baf75 versions update
• 5797233 sample app change
• e921988 Update README.md
• 421a207 Update README.md
• 84e850e Update README.md
• 5137d58 small kdoc improvement
• ca1e9f9 fix lint
• b4c9335 target java 11
• Additional commits viewable in compare view

Updates io.github.raamcosta.compose-destinations:ksp from 1.9.40-beta to 1.9.53

Release notes

Sourced from io.github.raamcosta.compose-destinations:ksp's releases.

1.9.53

Versions update

• Compose 1.5.1
• Kotlin 1.9.10
• Jetpack Compose Navigation 2.7.2

Full Changelog: raamcosta/compose-destinations@1.9.52...1.9.53

1.9.51

• Dependencies updates

1.9.50 No longer beta! 🙌 No more accompanist-navigation! 🎉

Removed accompanist navigation since animations were imported to official compose navigation! 🎉

Because of this, some minor changes had to be made:

• DestinationStyleAnimated -> DestinationStyle.Animated
• rememberAnimatedNavHost -> rememberNavHost
• rememberAnimatedNavHostEngine -> rememberNavHostEngine (unless you are using bottom sheet destinations, in which case you still need to use rememberAnimatedNavHostEngine)
• ExperimentalAnimationApi removed on most APIs
• If you were not using DestinationsNavHost:
  • AnimatedNavHost -> NavHost
  • animatedComposable -> composable
• You no longer need animations-core unless you are using BottomSheet destinations (which still is using accompanist material under the hood)
• If you do still use animations-core, even if you don't need BottomSheet, it's totally fine, using rememberAnimatedNavHostEngine will just internally call rememberNavHostEngine.

No beta suffix? 🤔

Yes, that's right, there were a lot of insecurities hiding behind that "-beta" suffixed on all the lib's versions. The truth is that API changes might happen but each version is stable for production. This is especially annoying because some developers have company policies that state they cannot use this library because of this. So from now on, if big changes happen I will create alpha, beta, rc releases (not necessarily all three, as it seems quite unnecessary most of the time) related to that specific version, basically following practices that you might be used to with other jetpack libraries and such.

Thanks for being with me through this time, Compose Destinations is just getting started! Look forward to v2 which I honestly think will be great!

1.9.42-beta

Fixes

• Fixed #415 - issue that was happening if you were not using animations core.

Full Changelog: raamcosta/compose-destinations@1.9.41-beta...1.9.42-beta

Commits

• 86b5af3 versions update
• 81fc817 versions update
• e2baf75 versions update
• 5797233 sample app change
• e921988 Update README.md
• 421a207 Update README.md
• 84e850e Update README.md
• 5137d58 small kdoc improvement
• ca1e9f9 fix lint
• b4c9335 target java 11
• Additional commits viewable 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)

[github-actions]

Test Results

12 tests   - 611   12 ✔️  - 610   0s ⏱️ - 8m 53s
  3 suites  -   87     0 💤  -     1 
  3 files    -   87     0 ❌ ±    0 

Results for commit f05f561. ± Comparison against base commit 7e2d2de.

This pull request removes 611 tests.

com.wire.android.GlobalObserversManagerTest ‑ given few valid accounts, when starting observing accounts, then create user-specific notification channels()
com.wire.android.GlobalObserversManagerTest ‑ given valid accounts, at least one with persistent socket enabled, and socket service running, then do not start service again()
com.wire.android.feature.AccountSwitchUseCaseTest ‑ givenCurrentSessionIsInvalid_whenSwitchingToAccount_thenUpdateCurrentSessionAndDeleteTheOldOne()
com.wire.android.feature.AccountSwitchUseCaseTest ‑ givenCurrentSessionIsValidAndNoOtherSessions_whenTryToSwitchToNextAccount_thenUpdateCurrentSessionAndReturnSuccessNoMoreAccounts()
com.wire.android.feature.AccountSwitchUseCaseTest ‑ givenCurrentSessionIsValid_whenSwitchingToAccountIsCalled_thenUpdateCurrentSessionAndReturnSuccessSwitchedToAnotherAccount()
com.wire.android.feature.GenerateRandomPasswordUseCaseTest ‑ Given GenerateRandomPasswordUseCase, when generating a password, then it should meet the specified criteria()
com.wire.android.feature.GenerateRandomPasswordUseCaseTest ‑ Given character sets, when accessing allCharacters, then it should return the expected value()
com.wire.android.feature.GenerateRandomPasswordUseCaseTest ‑ Given character sets, when accessing digits, then it should return the expected value()
com.wire.android.feature.GenerateRandomPasswordUseCaseTest ‑ Given character sets, when accessing lowercase, then it should return the expected value()
com.wire.android.feature.GenerateRandomPasswordUseCaseTest ‑ Given character sets, when accessing specialChars, then it should return the expected value()
…

[AndroidBob]

Build 1122 failed.

[vitorhugods]

Closing for now, as it requires some manual work :)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.