Releases: bitPogo/kmock
Releases · bitPogo/kmock
v0.3.0-rc08
Bumped
- Kotlin 1.7.22 -> 1.8.0
- AtomicFU 0.18.5 -> 0.19.0
- KSP 1.7.22-1.0.8 -> 1.8.0-1.0.8
v0.3.0-rc07
Bumped
- Kotlin 1.7.21 -> 1.7.22
- KSP 1.7.21-1.0.8 -> 1.7.22-1.0.8
v0.3.0-rc06
Bumped
- Kotlin 1.7.20 -> 1.7.21
- KSP 1.7.20-1.0.6 -> 1.7.21-1.0.8
v0.3.0-rc05
Added
- support for Kotlin Apple Targets and mingwX64
Bumped
- Kotlin 1.7.10 -> 1.7.20
- AtomicFu 0.18.3 -> 0.18.5
- KSP 1.7.10-1.0.6 -> 1.7.20-1.0.6
- Android Gradle Plugin 7.3.0 -> 7.3.1
v0.3.0-rc04
Bumped
- Gradle 7.5 -> 7.5.1
- Kotlin 1.7.0 -> 1.7.10
- AtomicFu 0.18.2 -> 0.18.3
- Android Target SDK 32 -> 33
- KSP 1.7.0-1.0.6 -> 1.7.10-1.0.6
v0.3.0-rc03
Changed
- pseudo build-in methods are now resolved independently
Fixed
- Aliases as type arguments are not correctly resolved, if the Aliases have type arguments on their own
- Generics cause AccessMethods to collide in their definition
- Stackoverflow when determine TypeVariance
- Unrelated MetaSources caused NPE
Bumped
- Gradle 7.4.2 -> 7.5
- Kotlin 1.6.21 -> 1.7.0
- KotlinPoet 1.11.0 -> 1.12.0
- AtomicFu 0.17.3 -> 0.18.2
- Stately 1.2.1 -> 1.2.3
- Android Target SDK 31 -> 32
- CompilerTest 1.4.8 -> 1.4.9
v0.3.0-rc02
Changed
- sources for
release
anddebug
for non KMP are now added via the Android extension while custom build-variant need manual setup
Fixed
- when Build Cache is enabled, Mocks are not created
- Relaxer not picked correctly up on multiple test runs
- Multi Interface Cleanup causes compilation to fail
Bumped
- Android Target SDK 31 -> 32
v0.3.0-rc01
Added
preventResolvingOfAliases
as workaround for AccessMethods with expect/actual Aliases which cause incremental builds to fail
Bumped
- Kotlin 1.6.10 -> 1.6.21
- AtomicFu 0.17.1 -> 0.17.3
- KSP 1.6.10-1.0.4 -> 1.6.21-1.0.6