From 5581c54cc527814d271a06c311b483cbf77c1d49 Mon Sep 17 00:00:00 2001 From: "sentry-junior[bot]" <264270552+sentry-junior[bot]@users.noreply.github.com> Date: Tue, 21 Jul 2026 23:15:44 +0000 Subject: [PATCH] docs(size-analysis): Mark build-configuration as optional Align upload metadata docs with CLI, Fastlane, and API behavior, where build-configuration is optional and used to keep size comparisons like-for-like across build variants. Co-Authored-By: Max Topolsky --- docs/product/size-analysis/integrating-into-ci.mdx | 2 +- includes/size-analysis/upload-metadata.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/product/size-analysis/integrating-into-ci.mdx b/docs/product/size-analysis/integrating-into-ci.mdx index 5a3c10e2d3eeb..2c06b6ddb7300 100644 --- a/docs/product/size-analysis/integrating-into-ci.mdx +++ b/docs/product/size-analysis/integrating-into-ci.mdx @@ -180,7 +180,7 @@ Check that: - You're correctly uploading builds for size analysis from all base branch builds - You're correctly uploading builds for size analysis from the PR branch. - Your builds that you want to compare have the same build configuration (for example, both are `Release` builds) -- Your builds contain all the [required metadata](/product/size-analysis/#upload-metadata) +- Your builds include the expected [upload metadata](/product/size-analysis/#upload-metadata) ### Missing Base Build diff --git a/includes/size-analysis/upload-metadata.mdx b/includes/size-analysis/upload-metadata.mdx index 258b60de36589..e994e12391500 100644 --- a/includes/size-analysis/upload-metadata.mdx +++ b/includes/size-analysis/upload-metadata.mdx @@ -4,7 +4,7 @@ We use build metadata to organize builds in the UI and ensure correct comparison | ----------------------- | --------------------------------------------------------------------------------------------------------- | | `org`\* | Sentry organization slug | | `project`\* | Sentry project slug | -| `build-configuration`\* | Build configuration describing how the app was built, for example `Release` or `Debug` or `Release-Bazel` | +| `build-configuration` | Build configuration describing how the app was built, for example `Release`, `Debug`, or an Android build variant like `freeRelease`. Recommended so size comparisons stay like-for-like across variants. | | `head-sha` | Current commit SHA | | `base-sha` | Base commit SHA (for comparisons, recommended to use the branch's merge-base) | | `vcs-provider` | VCS provider name (for example `github`, `gitlab`, `bitbucket`, `azure`, `github_enterprise`). If not provided, the provider will be auto-detected from the git remote URL. Note: Only `github` and `github_enterprise` are supported for status checks. |