Files
Bitsy 6c3bfd8679 chore(deps): coil 3.6.2 -> 3.6.3, ktor 3.5.2 -> 3.6.0
Sweep of every pin the project owns. Only these two moved:
- coil: COIL_REF bumped with it and the vendored sources re-synced (no
  local edits needed)
- ktor: plain Maven dep, apidemo's HTTP client

Already latest, left alone: SDL3 (release-3.4.16), koin 4.2.2, okio
3.18.2, coroutines 1.11.0, kotlinx-io-okio 0.9.1. Deliberately not
bumped: kotlinx-serialization (latest is 1.12.0-RC, a prerelease) and
everything under policy 1, which CMP 1.12.1 still pins where we are.

The pulse group rename also lands in the klib dumps here - the unique
name embeds the group, and BCV infers the macOS dumps from the checked-in
files on Windows, so those headers had to be rewritten for apiDump to run.
2026-09-22 15:51:26 +02:00

31 lines
1.6 KiB
Properties

# Pinned upstream refs for the vendored Compose sources. Referenced from each
# module's compose-fork.txt as SET_REPO=<url>@<VARNAME>. Bump a ref here and
# re-run scripts/compose-fork/sync.sh to re-sync everything to it.
# JetBrains/compose-multiplatform-core -- pinned to the durable TAG (fetchable by name
# from any fresh clone, unlike a bare unreferenced SHA which upstream could GC).
# 2026-09-22: v1.12.1. Both repos carry a clean `v1.12.1` tag and the matching
# artifacts are on Maven Central, so the native (vendored) side and the JVM
# parity leg stay in lockstep - no dev-build skew to document. The JVM forcing
# lives in gradle/libs.versions.toml (`compose`), which must stay equal to this
# ref's base version. skiko is unchanged at 0.150.1, so the mingw fork still
# matches its Skia base.
COMPOSE_CORE_REF=v1.12.1
# JetBrains/compose-multiplatform (umbrella repo -- :components-resources runtime)
COMPOSE_REF=v1.12.1
# InsertKoinIO/koin -- the DI layer. koin-core itself publishes mingwX64 + linux
# klibs and is consumed from Maven as-is; only the viewmodel / compose modules
# stop at apple+android upstream, so those are vendored.
KOIN_REF=4.2.2
# coil-kt/coil -- image loading. coil-core / coil / coil-svg / coil-network-*
# publish linux but NOT mingwX64; the compose layer publishes neither. The code
# is target-agnostic, so vendoring is mostly re-declaring the targets.
COIL_REF=3.6.3
# bitsycore/pulse-mvi -- the MVI layer. Targets android / jvm / ios / js / wasm
# upstream, with NO macos / linux / mingw, so all four modules are vendored.
PULSE_REF=0.3.7