Merge release/1.27.0 into main#574
Merged
Merged
Conversation
…1.27.0 Next dev iteration 1.27.0
# Conflicts: # buildSrc/src/main/kotlin/com/datadog/gradle/config/MavenConfig.kt
…-1.26.0-to-develop Merge release 1.26.0 to develop
Update Datadog Gradle Plugin to version 1.26.0
…pose-instrumentation-to-android-compilations RUM-16082: Limit Jetpack Compose instrumentation only to Android compilations
…nctionalTest, shorten their lifetime as well
…-oom-test-plugin RUM-16046: Fix oom in test:plugin
…sis-template-version-060526 Update static analysis template version
…-buildsrc-to-convention RUM-16183: Move from `buildSrc` to isolated build plugins module
Update Datadog SDK to version 3.10.0 Co-authored-by: satween <timur.valeev@datadoghq.com>
…eddable-from-main-module Remove Kotlin Compiler Embeddable from the dependencies of the main plugin module
Co-authored-by: Cursor <cursoragent@cursor.com>
…n-automatically-created-commits RUM-15945: Sign automatically created commits
Routes Gradle dependency and plugin resolution through Datadog's internal Magic Mirror Depot (depot-read-api-java) when running in GitLab CI, to eliminate HTTP 429 rate-limits from public registries.
The change is gated behind two Gradle properties (mavenRepositoryProxy, gradlePluginProxy) that are only set in CI via .gitlab-ci.yml. Local builds with no properties set are a strict no-op; the existing public registries (mavenCentral, gradlePluginPortal, google, jitpack) remain as fallbacks in every repositories { } block.
Follows the same approach as DataDog/dd-sdk-android#3452 (which mirrors DataDog/dd-trace-java#9351 and #9802 — switching property injection from gradle.properties file writes to ORG_GRADLE_PROJECT_* environment variables).
Verified end-to-end with a clean-room test (isolated GRADLE_USER_HOME): every fresh artifact download routes through the depot, with no traffic to public registries.
RUM-16378: Resolve dependencies through Magic Mirror Depot in CI
Refactor compiler test infrastructure to support pluggable registrar APIs
Bump Kotlin version to 2.3.20 for the project
OkHttpUploader never set readTimeout, leaving it at OkHttp's 10-second default. For large mapping files (400+ MB), the server takes longer than 10s to process the received payload before sending an HTTP response, causing SocketTimeoutException: Read timed out even though the upload succeeded. Set readTimeout to NETWORK_TIMEOUT_MS (120s) to match the existing writeTimeout and connectTimeout. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ead-timeout-mapping-upload RUMS-6028: Set `readTimeout` on `OkHttpClient` to match `writeTimeout`
Setup kotlin24 module to support kotlin 2.4
Implement Kotlin 2.4 KCP support for Compose instrumentation
Merge feature/kotlin24 into develop
Prepare release 1.27.0
0xnm
approved these changes
Jun 11, 2026
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #574 +/- ##
=============================================
- Coverage 88.99% 73.81% -15.18%
- Complexity 42 294 +252
=============================================
Files 5 40 +35
Lines 109 1195 +1086
Branches 5 141 +136
=============================================
+ Hits 97 882 +785
- Misses 7 247 +240
- Partials 5 66 +61
🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
What does this PR do?
Merge release/1.27.0 into main
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)