mirror of
https://github.com/vitorpamplona/amethyst.git
synced 2026-10-06 03:38:23 +00:00
Claude
10336d8ed4
Sweep every dependency coordinate in the version catalog, the hardcoded
ones in amethyst/build.gradle.kts, the Gradle wrapper and the GitHub
Actions against their upstream metadata, and take the newest release
that keeps each pin on the same stability channel it was already on.
Version catalog:
appcompat 1.7.1 -> 1.8.0
benchmark 1.5.0-alpha07 -> 1.5.0-rc01
biometricKtx 1.2.0-alpha05 -> 1.4.0-alpha02
composeBom 2026.06.01 -> 2026.08.00
composeRuntimeAnnotation 1.11.4 -> 1.12.0
composemediaplayer 0.11.3 -> 0.11.4
firebaseBom 34.16.0 -> 34.17.0
fragmentKtx 1.8.9 -> 1.9.0
ksp 2.3.10 -> 2.3.11
ktor 3.5.1 -> 3.5.2
media3 1.10.1 -> 1.11.0
secp256k1KmpJniAndroid 0.23.0 -> 0.24.0
uiautomator 2.3.0 -> 2.4.0
webkit 1.16.0 -> 1.17.0
composeRuntimeAnnotation is not an independent choice: the 2026.08.00
BOM pins runtime/foundation at 1.12.0, so the standalone annotation
artifact has to move with it.
A shared version ref can only advance to the lowest release available
across every artifact that uses it. `appfunctions` is the one ref here
where the artifacts do not publish in lockstep: `appfunctions` and
`appfunctions-compiler` are at alpha10 but `appfunctions-service` stops
at alpha09, so the ref stays at alpha09 and a comment now records the
cap. Every other multi-artifact ref (media3, secp256k1, ktor, benchmark,
coil, camera, ...) agrees across all of its artifacts.
Hardcoded in amethyst/build.gradle.kts:
tink-android 1.17.0 -> 1.23.0
tracing-perfetto(+binary) 1.0.0 -> 1.0.1
Gradle wrapper 9.5.0 -> 9.7.0 (distributionSha256Sum updated to the
checksum published for 9.7.0), and actions/setup-java v5.6.0 -> v5.7.0
across build, create-release and smoke-test-desktop. Every other action
already floats on its current major tag.
Left alone on purpose:
- vico stays at 3.2.3; the only newer build is the 3.3.0-next.2
prerelease and the current pin is stable.
- negentropy-kmp stays at v1.2.0, already the newest; the 1.0.1 that
shows up in Maven metadata is an older artifact under a different
tag scheme.
- AGP, Kotlin, compose-multiplatform and the JetBrains material3 pin
are all already the latest stable; newer builds are alphas/RCs.
- The @moq/* npm pins in nestsClient/tests/browser-interop, because
that directory's REV file ties the 0.2.x (moq-lite-03) line to the
moq-relay git rev pinned in hang-interop/REV. Bumping to 0.3.x is a
wire-protocol change that has to move with the Rust relay pin.
No new dependencies are introduced, so no new licenses enter the build.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013UYmEazSQkEwsVCvrG96mB