Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.12
->8.12.1
1.69.0
->1.70.0
1.69.0
->1.70.0
0.5.0-grpc-6
->0.5.1-grpc-16
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
3.0.3
->3.1.0
1.8.0-alpha01
->1.8.0-SNAPSHOT+pull-1739
1.7.6
->1.7.8
1.7.6
->1.7.8
0.5.0-grpc-6
->0.5.1-grpc-16
1.7.6
->1.7.8
1.7.6
->1.7.8
1.7.6
->1.7.8
1.7.6
->1.7.8
1.7.6
->1.7.8
1.9.3
->1.10.0
2025.1.2
->2025.2.4
8.8.0-alpha05
->8.8.0
8.8.0-alpha05
->8.8.0
Release Notes
gradle/gradle (gradle)
v8.12.1
Compare Source
grpc/grpc-java (io.grpc:protoc-gen-grpc-java)
v1.70.0
Bug Fixes
8ea3629
). Violations would only have triggered on API level 23 and earlier, and the violations fixed here were highly unlikely to be triggeredebe2b48
). This fixes a regression introduced in 1.64.0. The regression should have caused failures on API level 23 and earlier when a StatusRuntimeException or StatusException was created. However, for unknown reasons tests on old devices didn’t notice issuesa0982ca
). Hostnames are considered trusted and CAs are required to use punycode for non-ASCII hostnames, so this is expected to provide defense-in-depth. See also the related GoSecure blog post and the AOSP fix65b32e6
)1cf1927
). This (along with6c12c2b
) fixes a nonce-handling regression introduced in 1.66.0 that could cause resources to appear to not exist until re-creating the ADS stream. Triggering the behavior required specific config changes. It is easiest to trigger when clusters use EDS and routes are changed from one cluster to another. The error “found 0 leaf (logical DNS or EDS) clusters for root cluster” might then be seen6c12c2b
)e8ff6da
). They were previously required to be strings6516c73
). This fixes the error “Incorrect number of required labels provided. Expected: 4” introduced in 1.69.0f8f6139
). This fixes clients treating large max_requests as “no requests” and failing all requestsImprovements
0b2d440
)ea8c31c
)805cad3
)1126a8e
)ef7c2d5
)1edc4d8
). Not used actively, but this adds validation. The validation is unlikely to fail but may reject invalid resources.ebb43a6
). This only impacts thegrpc.target
label ingrpc.xds_client.*
metrics. Previously the empty string was used7f9c1f3
). This only matters when debug logging is enabledDocumentation
f1109e4
)c96e926
)5e8abc6
)Dependencies
8a5f777
)Thanks to
v1.69.1
Bug Fixes
a0982ca
). Hostnames are considered trusted and CAs are required to use punycode for non-ASCII hostnames, so this is expected to provide defense-in-depth. See also the related GoSecure blog post and the AOSP fix1cf1927
). This (along with6c12c2b
) fixes a nonce-handling regression introduced in 1.66.0 that could cause resources to appear to not exist until re-creating the ADS stream. Triggering the behavior required specific config changes. It is easiest to trigger when clusters use EDS and routes are changed from one cluster to another. The error “found 0 leaf (logical DNS or EDS) clusters for root cluster” might then be seen6c12c2b
)e8ff6da
). They were previously required to be stringsf8f6139
). This fixes clients treating large max_requests as “no requests” and failing all requests6516c73
). This fixes the error “Incorrect number of required labels provided. Expected: 4” introduced in 1.69.0ktorio/ktor (io.ktor:ktor-client-js)
v3.1.0
Features
Improvements
receiveMultipart
throws IllegalStateException instead of UnsupportedMediaTypeException (KTOR-7470)bind
overload withhostName
andport
(KTOR-7663)Bugfixes
JetBrains/compose-jb (org.jetbrains.compose)
v1.8.0-alpha03
Changes since 1.8.0-alpha02
Highlights
Multiple Platforms
BackHandler
andPredictiveBackHandler
. And use them in material3 widgets and androidx-navigation libraryBreaking Changes
Multiple Platforms
iOS
CupertinoScrollDecayAnimationSpec
andCupertinoOverscrollEffect
are removed from public APIFeatures
Multiple Platforms
Clipboard
interface with suspend functions, which work correctly on all targets including Web. TheClipboardManager
was deprecated because it was not possible to correctly implement it for WebiOS
AccessibilitySyncOptions
removed. The accessibility tree is built on demandUIAccessibilityContainerTypeSemanticGroup
for traversal groupsUIScrollView
s, as well as withinUIScrollView
sFixes
Multiple Platforms
placeWithLayer
scale application: offset is not scaled now (Android behavior)captureToImage
iOS
UIMenu
that appears over the Compose contentDesktop
Modifier.semantics { hideFromAccessibility() }
should now be correctly hidden from a11yTextField(TextFieldState)
(akaBasicTextField2
)TextField(TextFieldState)
(akaBasicTextField2
)Modifier.selectable
withRole.RadioButton
will have their state reported to accessibility viaAccessibleValue.getCurrentAccessibleValue()
and asAccessibleState.CHECKED
ingetAccessibleStateSet()
Web
BasicTextField
handles browser copy/cut/paste events correctly now. Previously, they were ignoredDependencies
Gradle Plugin
org.jetbrains.compose
, version1.8.0-alpha03
. Based on Jetpack Compose libraries:Lifecycle libraries
org.jetbrains.androidx.lifecycle:lifecycle-*:2.9.0-alpha03
. Based on Jetpack Lifecycle 2.9.0-alpha03Navigation libraries
org.jetbrains.androidx.navigation:navigation-*:2.8.0-alpha13
. Based on Jetpack Navigation 2.8.4Material3 Adaptive libraries
org.jetbrains.compose.material3.adaptive:adaptive*:1.1.0-alpha03
. Based on Jetpack Material3 Adaptive 1.1.0-beta01v1.8.0-alpha02
Changes since 1.8.0-alpha01
Highlights
Resources
FontVariation.Settings
support to the resources libraryFeatures
iOS
Web
PointerIcon.fromKeyword
function to change the browser cursorFixes
Multiple Platforms
ModalDrawerSheet
overload withDrawerState
argumentiOS
UIKitInteropInteractionMode.Cooperative
interaction modeUINavigationController
should recognize correctlyoptOutOfCupertinoOverscroll()
removedDesktop
Dialog
/Popup
creation in case ofcompose.layers.type=COMPONENT
and pointingwindowContainer
toComposePanel
itselfcompose.interop.blending
flag (1.7.0 regression)Resources
Navigation
Dependencies
Gradle Plugin
org.jetbrains.compose
, version1.8.0-alpha02
. Based on Jetpack Compose libraries:Lifecycle libraries
org.jetbrains.androidx.lifecycle:lifecycle-*:2.9.0-alpha02
. Based on Jetpack Lifecycle 2.9.0-alpha03Navigation libraries
org.jetbrains.androidx.navigation:navigation-*:2.8.0-alpha12
. Based on Jetpack Navigation 2.8.4Material3 Adaptive libraries
org.jetbrains.compose.material3.adaptive:adaptive*:1.1.0-alpha02
. Based on Jetpack Material3 Adaptive 1.1.0-alpha07Kotlin/kotlinx-rpc (org.jetbrains.kotlinx.rpc.plugin)
v0.5.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
This PR was generated by Mend Renovate. View the repository job log.