test(plugins): select latest unversioned dependency range#9352
Conversation
Overall package sizeSelf size: 6.77 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.3.1 | 122.62 kB | 438.86 kB | | opentracing | 0.14.7 | 194.81 kB | 194.81 kB | | dc-polyfill | 0.1.11 | 25.74 kB | 25.74 kB |🤖 This report was automatically generated by heaviest-objects-in-the-universe |
🎉 All green!🧪 All tests passed 🔄 Datadog auto-retried 1 job - 1 passed on retry 🎯 Code Coverage (details) 🔗 Commit SHA: 8cdaaa8 | Docs | Datadog PR Page | Give us feedback! |
BenchmarksBenchmark execution time: 2026-07-16 00:29:26 Comparing candidate commit 8cdaaa8 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 2320 metrics, 38 unstable metrics.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #9352 +/- ##
========================================
Coverage 96.64% 96.64%
========================================
Files 923 923
Lines 122844 122844
Branches 21042 21227 +185
========================================
+ Hits 118725 118726 +1
+ Misses 4119 4118 -1 Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Runtime-gated declarations could leave the first active range as the unversioned target even when a newer compatible range was also active.
d28a349 to
94cf8a3
Compare
Runtime-gated declarations could leave the first active range as the unversioned target even when a newer compatible range was also active.
Runtime-gated declarations could leave the first active range as the unversioned target even when a newer compatible range was also active.
Runtime-gated declarations could leave the first active range as the unversioned target even when a newer compatible range was also active.
Runtime-gated declarations could leave the first active range as the unversioned target even when a newer compatible range was also active.
Summary
Runtime-gated declarations could leave the first active range as the unversioned target even when a newer compatible range was also active. Resolve same-package declarations together so dependency installation selects the newest active range.
Why
Common versions can stay in one declaration while runtime-specific additions remain separate, without duplicating ranges to preserve the default target.