renovate: update major-risky-update

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Age	Adoption	Passing	Confidence
actions/checkout	action	major	v4 -> v5
actions/setup-java	action	major	v4 -> v5
github/codeql-action	action	major	v3 -> v4
gradle (source)		major	8.14 -> 9.2.0
gradle/actions	action	major	v4 -> v5
com.stripe:stripeterminal-core	dependencies	major	3.10.2 -> 4.7.4
io.insert-koin:koin-androidx-compose (source)	dependencies	major	3.5.6 -> 4.1.1
co.touchlab.kmmbridge	plugin	major	0.5.5 -> 1.2.1
org.orbit-mvi:orbit-core	dependencies	major	8.0.0 -> 10.0.0
org.orbit-mvi:orbit-compose	dependencies	major	8.0.0 -> 10.0.0
io.insert-koin:koin-android (source)	dependencies	major	3.5.6 -> 4.1.1
io.insert-koin:koin-core (source)	dependencies	major	3.5.6 -> 4.1.1

---

Release Notes

actions/checkout (actions/checkout)

v5

Compare Source

actions/setup-java (actions/setup-java)

v5

Compare Source

github/codeql-action (github/codeql-action)

v4

Compare Source

gradle/gradle (gradle)

v9.2.0

Compare Source

v9.1.0: 9.1.0

Compare Source

The Gradle team is excited to announce Gradle 9.1.0.

Here are the highlights of this release:

• Full Java 25 support
• Native task graph visualization
• Enhanced console output

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Eng Zer Jun,
EunHyunsu,
Gaëtan Muller,
HeeChul Yang,
Jendrik Johannes,
Johnny Lim,
Junho Lee,
Kirill Gavrilov,
Matthew Haughton,
Na Minhyeok,
Philip Wedemann,
Philipp Schneider,
Pradyumna C,
r-a-sattarov,
Ryszard Perkowski,
Sebastian Schuberth,
SebastianHeil,
Staffan Al-Kadhimi,
winfriedgerlach,
Xin Wang.

Upgrade instructions

Switch your build to use Gradle 9.1.0 by updating your wrapper:

./gradlew wrapper --gradle-version=9.1.0 && ./gradlew wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v9.0.0: 9.0.0

Compare Source

The Gradle team is excited to announce Gradle 9.0.0.

Here are the highlights of this release:

• Configuration Cache is the recommended execution mode
• Gradle requires JVM 17 or higher to run
• Build scripts use Kotlin 2.2 and Groovy 4.0
• Improved Kotlin DSL script compilation avoidance

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aaron Matthis,
Adam E,
Adam S,
Björn Kautler,
Daniel Lacasse,
Eng Zer Jun,
EunHyunsu,
FlorianMichael,
Francisco Prieto,
Gaëtan Muller,
Jake Wharton,
Kengo TODA,
Kent Kaseda,
Madalin Valceleanu,
Marc Philipp,
Mark S. Lewis,
Matthew Haughton,
Mycroft Wong,
Na Minhyeok,
Nelson Osacky,
Olivier "Oli" Dagenais,
ploober,
Radai Rosenblatt,
Róbert Papp,
Sebastian Schuberth,
Victor Merkulov.

Upgrade instructions

Switch your build to use Gradle 9.0.0 by updating your wrapper:

./gradlew wrapper --gradle-version=9.0.0 && ./gradlew wrapper

See the Gradle 9.0.0 upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.14.3: 8.14.3

Compare Source

The Gradle team is excited to announce Gradle 8.14.3.

This is a patch release for 8.14. We recommend using 8.14.3 instead of 8.14.

Here are the highlights of this release:

• Java 24 support
• GraalVM Native Image toolchain selection
• Enhancements to test reporting
• Build Authoring improvements

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aurimas,
Ben Bader,
Björn Kautler,
chandre92,
Daniel Hammer,
Danish Nawab,
Florian Dreier,
Ivy Chen,
Jendrik Johannes,
jimmy1995-gu,
Madalin Valceleanu,
Na Minhyeok.

Upgrade instructions

Switch your build to use Gradle 8.14.3 by updating your wrapper:

./gradlew wrapper --gradle-version=8.14.3 && ./gradlew wrapper

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.14.2: 8.14.2

Compare Source

The Gradle team is excited to announce Gradle 8.14.2.

Here are the highlights of this release:

• Java 24 support
• GraalVM Native Image toolchain selection
• Enhancements to test reporting
• Build Authoring improvements

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aurimas,
Ben Bader,
Björn Kautler,
chandre92,
Daniel Hammer,
Danish Nawab,
Florian Dreier,
Ivy Chen,
Jendrik Johannes,
jimmy1995-gu,
Madalin Valceleanu,
Na Minhyeok.

Upgrade instructions

Switch your build to use Gradle 8.14.2 by updating your wrapper:

./gradlew wrapper --gradle-version=8.14.2 && ./gradlew wrapper

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.14.1: 8.14.1

Compare Source

The Gradle team is excited to announce Gradle 8.14.1.

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aurimas,
Ben Bader,
Björn Kautler,
chandre92,
Daniel Hammer,
Danish Nawab,
Florian Dreier,
Ivy Chen,
Jendrik Johannes,
jimmy1995-gu,
Madalin Valceleanu,
Na Minhyeok.

Upgrade instructions

Switch your build to use Gradle 8.14.1 by updating your wrapper:

./gradlew wrapper --gradle-version=8.14.1 && ./gradlew wrapper

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

gradle/actions (gradle/actions)

v5

Compare Source

stripe/stripe-terminal-android (com.stripe:stripeterminal-core)

v4.7.4

Core

Fixes

• Resolves compatibility issues with kotlinx.datetime 0.7.0+. Fixes issue 611.

v4.7.3

Tap to Pay

Fixes

• Addresses issues where a device may erroneously report as not being compatible with Tap to Pay on Android, or fail during the Tap to Pay on Android connection process with a KEY_ERROR. Fixes issue 629.

v4.7.2

Core

Fixes

• Fixes an issue that caused the "Application Not Responding" (ANR) error that occurred during Terminal SDK initialization on certain Android devices.

v4.7.1

Tap to Pay

Fixes

• Addresses 16KB page alignment issue. Fixes issue 577.

v4.7.0

Core

New

• Improved visibility into mobile reader disconnects by exposing new disconnect reasons: DisconnectReason.BLUETOOTH_PEER_REMOVED_PAIRING_INFORMATION

Fixes

• Fixed an issue where the SDK fails to forward offline payments due to expired connection tokens. The SDK will now automatically refresh the connection token when it expires, allowing offline payments to be forwarded without interruption.

v4.6.0

Tap to Pay

Updates

• For tablets, the payment collection screen now respects the device's orientation, and is no longer restricted to landscape. For phones, the orientation will still be locked to portrait. Fixes issue 565.

Fixes

• Resolved a KeyStore issue that would result in an "Error setting key entry during secure import" message when attempting to connect to the Tap to Pay reader on certain devices. Fixes issue 561.
• Resolved a network connectivity callback registration leak that could result in TooManyRequestsException after a long period of use. Fixes issue 576.

Apps on Devices: Handoff mode

Updates

• Operations that require a connected reader will fail with NOT_CONNECTED_TO_READER when the application is no longer connected to the reader.
• The SDK will automatically disconnect from the reader when a command results in a READER_COMMUNICATION_ERROR.

Fixes

• Fixed spurious error logs Handoff client received Legacy callback. Fixes issue 481.

v4.5.1

Tap to Pay

Fixes

• Addresses an issue that resulted in significantly reduced authorization rates for payments made with Tap to Pay on Android. Stripe highly discourages using Tap to Pay on Android 4.5.0 in any production environments. Fixes issue 596.

v4.5.0

Core

New

• Preview: Added ConfirmConfiguration.surcharge and SurchargeConfiguration to configure surcharging on confirmPaymentIntent.
  • If you are interested in joining this preview, please contact Stripe support.

Updates

• The Terminal.collectInputs method to display forms and collect information from customers is now generally available, and it no longer requires an opt-in annotation.
• Preview: The ConfirmConfiguration.amountSurcharge field has been renamed to ConfirmConfiguration.surcharge.amount.
  • If you are interested in joining this preview, please contact Stripe support.

Tap to Pay

Updates

• Improved messaging for Play Integrity API failures during the reader connection process. Fixes issue 580.

v4.4.0

Core

New

• Improved visibility into mobile reader disconnects by exposing new disconnect reasons: DisconnectReason.USB_DISCONNECTED, and DisconnectReason.IDLE_POWER_DOWN.

Fixes

• Terminal operations that require a connected reader (e.g. collectPaymentMethod) will now fail with TerminalErrorCode.NOT_CONNECTED_TO_READER when no reader is connected.

Tap to Pay

New

• Added a TapToPay.isInTapToPayProcess() method to help determine if the current process is the dedicated Tap to Pay process.

Fixes

• Gracefully handle device-to-device restore for apps that use the android:allowBackup="true" manifest tag. Fixes issue 513.
• Terminal.supportsReadersOfType() will now return false when checking Tap to Pay on Android compatibility for host devices that do not support certain hardware-backed KeyStore operations. Fixes issue 553.
• Prevent Tap to Pay reader connections from failing on devices without an accelerometer. Fixes issue 562.

v4.3.1

Core

• Fix: Prevent crashes in applications using newer versions of Sentry. Fixes issue 566.

v4.3.0

Core

• New: Added simulated internet reader support for collecting on-screen inputs. See the updated SimulatorConfiguration for usage.
• Preview: Added field requestPartialAuthorization to CardPresentOptions.
  • If you are interested in joining this preview, please email stripe-terminal-betas@stripe.com.
• New: Added field cardDetails to PaymentMethodDetails.
  • Note this requires reader software version 2.31 or later to be installed on your internet reader.
• Update: Added a new id parameter to collect input's SelectionButton to uniquely identify the button.

Tap to Pay

• New: On-screen PIN entry is now generally available on Tap to Pay Android.
• Breaking: When Tap to Pay Android PIN throws a TerminalException due to an insecure condition the exception will have a correct errorCode of TAP_TO_PAY_INSECURE_ENVIRONMENT instead of TAP_TO_PAY_DEVICE_TAMPERED.
• Fix: Prevent a StringIndexOutOfBoundsException crash on certain device models prior to showing the Tap to Pay payment screen. Fixes issue 533.
• Update: Improved error messaging when Tap to Pay on Android PIN fails due to an insecure condition.

v4.2.0

Core

• New: Added error code READER_TAMPERED for detecting if a mobile reader is tampered on connection.
• Fix: Addressed an issue where readers lose optional software updates after auto-reconnecting.

Tap to Pay

• New: HIDE_OVERLAY_WINDOW permission is now required for Tap to Pay to ensure a secure environment while operating.
• Fix: Allow the Tap to Pay reader to connect from applications that have enabled installer checks in Google Play. Fixes issue 866.
• Fix: Localization issues for Tap to Pay on Android PIN preview.

v4.1.0

Core

• Preview: Affirm support for smart readers is now available in private preview.
  • If you are interested in joining this preview, please email stripe-terminal-betas@stripe.com.
• New: Added a returnUrl parameter to ConfirmConfiguration to specify a desired URL to redirect to upon completion of a redirect payment method (such as Affirm).
• Update: Added support for operating offline with simulated Bluetooth and USB readers.
• Preview: Added a new enum value Manual to CardPresentCaptureMethod which will override the top level captureMethod set on the Paymentintent specifically for card_present transactions.
  • If you are interested in joining this preview, please email stripe-terminal-betas@stripe.com.
• Preview: Terminal::collectData will be supported on Smart readers.
  • Note: This feature requires reader software version 2.28 or later to be installed on your smart reader.
  • If you are interested in joining this preview, please email terminal-collect-data@stripe.com.
• Fix: Fixed an issue where, if the SDK was initialized offline and a user immediately attempts to pair a reader offline, the first attempt fails with "The selected reader requires a software update", despite the reader being up-to-date.

Tap to Pay

• New: Added error code TAP_TO_PAY_INSECURE_ENVIRONMENT for cases when payment collection is attempted in an insecure environment.

v4.0.0

4.0.0 includes breaking changes in both APIs and behavior. See the migration guide for more details.

Core

Add support for apps built with targetSdkVersion = 35 targeting Android 15 devices.

• Note: This update includes support for Tap to Pay on Android. Users who were previously advised not to upgrade can now safely target version 35.

New Features

• Mail order / telephone order (MOTO) payment support for smart readers.
  • Contact Stripe support to enable this feature on your account.
• Global card saving after payment support by updating customer consent capture. The following breaking changes are required:
  • Removed the customerConsentCollected parameter from Terminal::collectSetupIntentPaymentMethod and replaced it with allowRedisplay.
  • A valid allowRedisplay value is now required to be set in collectConfiguration when using setupFutureUsage for Terminal::collectPaymentMethod.

⚠️ Breaking changes required

Reader discovery

• New: Added a new enum value DISCOVERING to ConnectionStatus to represent when discovery is running.
• Update: InternetDiscoveryConfiguration now supports an optional timeout value, specifying the timeout in seconds for discover readers request. If the online discovery attempt fails, the operation automatically fall back to offline discovery.
• Update: If a new discover operation is initiated while one is already in progress, the SDK will now cancel the ongoing operation with a CANCELED_DUE_TO_INTEGRATION_ERROR error and start the new operation.
• Update: Internet and Tap to Pay discovery will now call the Callback.onSuccess method as part of discoverReaders when the operation completes since these are not long running discovery operations.
• Update: Fields on the Location object are no longer mutable.

Reader connection

• Update: There is now a single Terminal::connectReader method for all connection types. This replaces the previous methods: connectBluetoothReader, connectUsbReader, connectInternetReader, connectLocalMobileReader, and connectHandoffReader.
  • For mobile readers, the readerListener parameter has been removed from the old connectBluetoothReader, connectUsbReader methods and moved into the respective ConnectionConfiguration object, replacing ReaderReconnectionListener.
  • For Tap to Pay readers, the TapToPayConnectionConfiguration now takes in a TapToPayReaderListener parameter, replacing ReaderReconnectionListener.
  • For smart readers, InternetConnectionConfiguration now takes in an InternetReaderListener parameter, which will alert your integration of events such as reader disconnects.
  • For Apps on devices in handoff mode, HandoffReaderListener has been removed from the old connectHandoffReader method as a parameter, and moved into the HandoffConnectionConfiguration object.
• Update: Auto reconnect on unexpected disconnect is now enabled by default for mobile readers and Tap to Pay readers.
  • For mobile readers, ReaderListener has been renamed to MobileReaderListener and now extends ReaderReconnectionListener to provide a single interface for handling reader reconnection events.
  • For Tap to Pay readers, TapToPayReaderListener extends ReaderReconnectionListener to provide a single interface for handling reader reconnection events.
  • The ReaderReconnectionListener parameter has been removed from the connection configurations: LocalMobileConnectionConfiguration, BluetoothConnectionConfiguration, and UsbConnectionConfiguration.
  • Auto-reconnect is now supported for simulated mobile readers. Users can now trigger events, such as ReaderReconnectionListener::onReaderReconnectStarted, by invoking Terminal::rebootReader.
  • The ReaderReconnectionListener::onReaderReconnectStarted event has been updated to always include the DisconnectReason parameter, indicating the possible reasons for a mobile reader disconnection. For other reader types, UNKNOWN will be returned.
• Update: The method for handling reader disconnects has changed.
  • The TerminalListener::onUnexpectedReaderDisconnect has been removed. Implement onDisconnect on any of the following listeners to be informed of their corresponding reader disconnects: InternetReaderListener, MobileReaderListener, TapToPayReaderListener, or HandoffReaderListener.
  • When auto-reconnect on unexpected disconnect is enabled, both onDisconnect and onReaderReconnectFailed methods will be called if the SDK fails to reconnect to the reader and it becomes disconnected.

Payment acceptance

• Update: Terminal::confirmPaymentIntent, Terminal::confirmSetupIntent, and Terminal::confirmRefund now return a Cancelable, which allows you to cancel the operation in certain scenarios, such as QR Code payment presentment.
• Update: Calls to Terminal::cancelPaymentIntent or Terminal::cancelSetupIntent will now cancel ongoing operations related to the specified intent.
• Fix: Calls to Terminal::collectSetupIntentPaymentMethod now updates the provided SetupIntent with the correct status of SetupIntentStatus.REQUIRES_CONFIRMATION, instead of SetupIntentStatus.REQUIRES_PAYMENT_METHOD. Fixes issue 449.
• Update: SetupIntent.id is now nullable to be consistent with Paymentintent.id. The SetupIntent.id will continue to be present.

Error handling

• Update: Moved TerminalException.TerminalErrorCode to a standalone enum TerminalErrorCode.
• Update: Introduced TerminalErrorCode.GENERIC_READER_ERROR. This error occurs when the SDK is out-of-date and can't map to a specific TerminalReaderError returned from a smart reader. The error message will be prefixed with "Error code: new_error_code."
  • Empty error codes still result in TerminalErrorCode.UNEXPECTED_SDK_ERROR, but error message will be prefixed with "Error code: unknown."
  • Known error codes continue to map to their corresponding TerminalErrorCode values, with unchanged error messages.

Renaming & refactoring

• Update: Renamed ReaderListener to MobileReaderListener.

• Renamed allowedPaymentMethodTypes to paymentMethodTypes:

  • PaymentIntentParameters::allowedPaymentMethodTypes has been removed and replaced with PaymentIntentParameters::paymentMethodTypes.
  • The allowedPaymentMethodTypes parameter in the PaymentIntentParameters.Builder constructors has been renamed to paymentMethodTypes.
  • SetupIntentParameters::allowedPaymentMethodTypes has been removed and replaced with SetupIntentParameters::paymentMethodTypes.
  • SetupIntentParameters.Builder::setAllowedPaymentMethodTypes has been removed and replaced with SetupIntentParameters.Builder::setPaymentMethodTypes.

• Update: in ReaderSoftwareUpdate, rename UpdateTimeEstimate to UpdateDurationEstimate, and timeEstimate to durationEstimate.

• Update: Converted java.util.Date references to timestamps in milliseconds for the following fields: ReaderSoftwareUpdate::requiredAt, OfflineDetails::storedAt and OfflineSetupIntentDetails::storedAt.

Tap to Pay

• Update: The Maven coordinates for the Tap to Pay on Android feature have changed to com.stripe:stripeterminal-taptopay:4.0.0. Please update your build dependencies to point to the new artifact name. The old one will no longer be updated.

• Update: SafetyNet Attestation API has been removed and replaced with Play Integrity API. Fixes issue 458.

• Update: TapToPayConnectionConfiguration now takes in a TapToPayReaderListener parameter. This listener inherits events from both ReaderReconnectionListener and ReaderDisconnectionListener, providing a unified interface for handling reader events.

• Update: The collectPaymentMethod and collectSetupIntentPaymentMethod now time out after 60 seconds for Tap to Pay on Android transactions. If a timeout occurs, a TerminalException will be raised with the error code CARD_READ_TIMED_OUT

• Update: When PIN collection is requested for a payment, a TerminalException will be raised with error code FEATURE_NOT_ENABLED_ON_ACCOUNT instead of DECLINED_BY_STRIPE_API with an ONLINE_OR_OFFLINE_PIN_REQUIRED ApiError.

• Update: Reduce the amount of time Terminal::connectReader takes to complete attestation.

• Update: Improve acceptance of some cards that previously would have displayed "Please use another card"

• Update: "Local Mobile" has been renamed to "Tap To Pay" in all function names and error codes to align with Stripe branding:

  • LocalMobileDiscoveryConfiguration has been renamed to TapToPayDiscoveryConfiguration.
  • LocalMobileConnectionConfiguration has been renamed to TapToPayConnectionConfiguration.
  • TapToPayConnectionConfiguration::localMobileReaderReconnectionListener has been renamed to TapToPayConnectionConfiguration::tapToPayReaderReconnectionListener.
  • LocalMobileUxConfiguration has been renamed to TapToPayUxConfiguration.
  • Terminal::setLocalMobileUxConfiguration has been renamed to Terminal::setTapToPayUxConfiguration.
  • TerminalErrorCode::LOCAL_MOBILE_LIBRARY_NOT_INCLUDED has been renamed to TerminalErrorCode::TAP_TO_PAY_LIBRARY_NOT_INCLUDED.
  • TerminalErrorCode::LOCAL_MOBILE_UNSUPPORTED_DEVICE has been renamed to TerminalErrorCode::TAP_TO_PAY_UNSUPPORTED_DEVICE.
  • TerminalErrorCode::LOCAL_MOBILE_UNSUPPORTED_ANDROID_VERSION has been renamed to TerminalErrorCode::TAP_TO_PAY_UNSUPPORTED_ANDROID_VERSION.
  • TerminalErrorCode::LOCAL_MOBILE_DEVICE_TAMPERED has been renamed to TerminalErrorCode::TAP_TO_PAY_DEVICE_TAMPERED.
  • TerminalErrorCode::LOCAL_MOBILE_DEBUG_NOT_SUPPORTED has been renamed to TerminalErrorCode::TAP_TO_PAY_DEBUG_NOT_SUPPORTED.
  • TerminalErrorCode::LOCAL_MOBILE_NFC_DISABLED has been renamed to TerminalErrorCode::TAP_TO_PAY_NFC_DISABLED.
  • DeviceType::COTS_DEVICE has been renamed to DeviceType::TAP_TO_PAY_DEVICE.

• The background application process used for collecting Tap to Pay transactions has been renamed to use your application's id, suffixed with :stripetaptopay.

InsertKoinIO/koin (io.insert-koin:koin-androidx-compose)

v4.1.1

Compare Source

Koin 4.1.1 Changelog

🐛 Bug Fixes

• Logger Constraint Revert - Reverted logger constraint due to compatibility issues causing errors across projects
• Maven Central Publication - Fixed publication issues for Maven Central distribution

💥 Breaking Changes for Internal

• Compose Scope Resolution - Fixed scope resolution issues in Compose integration with proper context handling, introduced ComposeContextWrapper to help manage internal scope state

🚀 Features & Improvements

• Compose ViewModel Navigation - Added optional navGraphRoute parameter to sharedKoinViewModel for better navigation support
• Compose Context Handling - Reworked LocalKoinApplication/LocalKoinScope with ContextWrapper to properly handle:
  • Scope closing lifecycle
  • Context restart scenarios
  • Better memory management

⚡ Performance & Core

• Core Resolver Optimization - Avoid unnecessary flattening operations when dealing with single scope resolution
• Scope Debugging - Enhanced scope debugging by showing linked scope IDs for better development experience
• Library Updates - Updated underlying dependencies to latest stable versions

📚 Library Updates

• Kotlin - Updated to 2.1.21 (from 2.1.20)
• Binary Validator - Updated to 0.18.1 (from 0.16.3)
• Ktor - Updated to 3.2.3 (from 3.1.3)
• Jetbrains Compose - Updated to 1.8.2 (from 1.8.0)
• AndroidX Libraries:
  • Fragment 1.8.9 (from 1.8.8)
  • WorkManager 2.10.3 (from 2.10.1)
  • Lifecycle 2.9.3 (from 2.9.0)
  • Navigation 2.9.3 (from 2.9.0)
  • JB Navigation RC01 (from Beta01)
• Testing:
  • Robolectric 4.15.1 (from 4.14.1)
  • Benchmark 0.4.14 (from 0.4.13)
• Build Tools - Added NMCP 1.1.0 for improved publication workflow

📦 Publication

• Multi-platform Artifacts - Ensured all platform variants are properly published
• Version Consistency - Synchronized all module versions across the ecosystem

🔧 Development

• Test Coverage - Added ActivityScopeArchetypeTest for better scope lifecycle testing
• API Stability - Maintained backward compatibility while fixing internal issues

👥 Contributors

https://github.com/arnaudgiuliani - Project Lead & Core Developer
https://github.com/rfaturriza - Community Contributor

New Contributors

• @​rfaturriza made their first contribution in #​2262

Full Changelog: InsertKoinIO/koin@4.1.0...4.1.1

v4.1.0

Compare Source

What's Changed

• Add Ktor3 Package by @​chrisjenx in #​1978
• Ktor requestscope function dsl by @​arnaudgiuliani in #​2075
• KoinApplication Multiplatform Config - Logger + Androic context automatic injection by @​arnaudgiuliani in #​2086
• [Maintenance] Github actions migrations by @​GrzegorzBobryk in #​2109
• KoinMultiplatformApplication - Compose Application Start + Native Context binding by @​arnaudgiuliani in #​2114
• Fix koininject signature by @​arnaudgiuliani in #​2154
• Wasm use std UUID by @​arnaudgiuliani in #​2159
• Feat - scope archetypes for Activity, Fragment & ViewModel by @​arnaudgiuliani in #​2169
• Feat - Shared ViewModel in navigation by @​arnaudgiuliani in #​2170
• remove toolchain param + gradle 8.9 + remove unused deps by @​arnaudgiuliani in #​2172
• Update Compose Multiplatform to 1.8.0-rc01 by @​zsmb13 in #​2179
• check optional parameters during dependency verification by @​luozejiaqun in #​2105
• Feat - AutoCloseable usage for VM Scope closure + ViewModel Scope creation at VM Factory (ctor injection) + Options activation by @​arnaudgiuliani in #​2181
• Feat - New Compose Preview function to help local preview with parallel … by @​arnaudgiuliani in #​2182
• Continue Compose Multiplatform 1.8 version upgrade by @​zsmb13 in #​2183
• Migration to lifecycle 2.9 by @​MatkovIvan in #​2184
• [CI] Introduce reusable action for job initialization by @​GrzegorzBobryk in #​2110
• [Maintenance] removal of @OptIn and @Suppress by @​GrzegorzBobryk in #​1996
• Fix - 4.1.0 beta8 build by [@​arnaudgiuliani](https://redirect.github.com/arnaudg

---

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 4am every weekday,every weekend" in timezone Europe/Vienna, 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.