chore: set Python-specific injection package size ratchet

[lloeki]

Description

Due to a change PHP-side libdatadog was bumped to v29. This version bump caused PHP images to blow past their previous limit.

Simultaneously, changes to the datadog-package binary were picked up. Notably the github.com/klauspost/compress/zstd dependency was bumped from 1.17.4 to 1.18.1. This bump included in 1.17.5 a default value change for the compression context size, downscaled from 32MB to 8MB (fixing compatibility with browsers like Chrome), causing drastic changes in compression results.

Unbeknownst to the second change, PHP therefore updated the global limits, attributing the size change to the libdatadog bump (which was true, but not for the whole of it):

• Container image limit changed from 190MB to 250MB
• OCI package limit changed from 130MB to 160MB

This allowed a change to slip through to other languages, where the new datadog-package binary caused regressions in package size without change to the inputs. Due to the wildly differing sizes of packages across languages the regression is silent, rendering the size threshold ratchet moot.

To combat such silently creeping regressions, this PR introduces language-specific thresholds for the ratchet through one pipeline overrides.

Testing

Shared pipeline should pass with the new thresholds in effect.

Risks

None

Additional Notes

datadog-package was fixed in https://github.com/DataDog/datadog-packages/pull/64 which may take some time to trickle down.

[KowalskiThomas]

Makes sense to me although I have little context; approving to unblock.

[brettlangdon]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-04-02 00:09:43 UTC ℹ️ Start processing command /merge

---

2026-04-02 00:09:48 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-04-02 04:55:08 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

[cit-pr-commenter-54b7da]

Codeowners resolved as

.gitlab-ci.yml                                                          @DataDog/python-guild @DataDog/apm-core-python