Bump kotlinx-coroutines-android from 1.3.0-RC2 to 1.3.2-1.3.60-eap-76

[dependabot-preview]

Bumps kotlinx-coroutines-android from 1.3.0-RC2 to 1.3.2-1.3.60-eap-76.

Release notes

Sourced from kotlinx-coroutines-android's releases.

1.3.2

This is a maintenance release that does not include any new features or bug fixes.

• Reactive integrations for Flow are promoted to stable API.
• Obsolete reactive API is deprecated.
• Deprecation level for API deprecated in 1.3.0 is increased.
• Various documentation improvements.

1.3.1

This is a minor update with various fixes:

• Flow: Fix recursion in combineTransform<T1, T2, R> (#1466).
• Fixed race in the Semaphore (#1477).
• Repaired some of ListenableFuture.kt's cancellation corner cases (#1441).
• Consistently unwrap exception in slow path of CompletionStage.asDeferred (#1479).
• Various fixes in documentation (#1496, #1476, #1470, #1468).
• Various cleanups and additions in tests.

Note: Kotlin/Native artifacts are now published with Gradle metadata format version 1.0, so you will need Gradle version 5.3 or later to use this version of kotlinx.coroutines in your Kotlin/Native project.

1.3.0

Flow

This version is the first stable release of Flow API.

All Flow API not marked with @FlowPreview or @ExperimentalCoroutinesApi annotations are stable and here to stay.
Flow declarations marked with @ExperimentalCoroutinesApi have the same guarantees as regular experimental API.
Please note that API marked with @FlowPreview have weak guarantees on source, binary and semantic compatibility.

Changelog

• A new guide section about Flow.
• CoroutineDispatcher.asExecutor extension (#1450).
• Fixed bug when select statement could report the same exception twice (#1433).
• Fixed context preservation in flatMapMerge in a case when collected values were immediately emitted to another flow (#1440).
• Reactive Flow integrations enclosing files are renamed for better interoperability with Java.
• Default buffer size in all Flow operators is increased to 64.
• Kotlin updated to 1.3.50.

Changelog

Sourced from kotlinx-coroutines-android's changelog.

Change log for kotlinx.coroutines

Version 1.3.2

This is a maintenance release that does not include any new features or bug fixes.

• Reactive integrations for Flow are promoted to stable API.
• Obsolete reactive API is deprecated.
• Deprecation level for API deprecated in 1.3.0 is increased.
• Various documentation improvements.

Version 1.3.1

This is a minor update with various fixes:

• Flow: Fix recursion in combineTransform<T1, T2, R> (#1466).
• Fixed race in the Semaphore (#1477).
• Repaired some of ListenableFuture.kt's cancellation corner cases (#1441).
• Consistently unwrap exception in slow path of CompletionStage.asDeferred (#1479).
• Various fixes in documentation (#1496, #1476, #1470, #1468).
• Various cleanups and additions in tests.

Note: Kotlin/Native artifacts are now published with Gradle metadata format version 1.0, so you will need
Gradle version 5.3 or later to use this version of kotlinx.coroutines in your Kotlin/Native project.

Version 1.3.0

Flow

This version is the first stable release with Flow API.

All Flow API not marked with @FlowPreview or @ExperimentalCoroutinesApi annotations are stable and here to stay.
Flow declarations marked with @ExperimentalCoroutinesApi have the same guarantees as regular experimental API.
Please note that API marked with @FlowPreview have weak guarantees on source, binary and semantic compatibility.

Changelog

• A new guide section about Flow.
• CoroutineDispatcher.asExecutor extension (#1450).
• Fixed bug when select statement could report the same exception twice (#1433).
• Fixed context preservation in flatMapMerge in a case when collected values were immediately emitted to another flow (#1440).
• Reactive Flow integrations enclosing files are renamed for better interoperability with Java.
• Default buffer size in all Flow operators is increased to 64.
• Kotlin updated to 1.3.50.

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 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)