ci: restore supported versions workflow - #9763
Conversation
## Summary - derive runtime entries from the release range and an optional narrower workflow range ## Why The removed workflow could push release-specific output to release branches, while the registry now expects per-runtime tested versions. Restricting the token job to same-repository, master-targeted, non-v*.x heads keeps release branches untouched. The known v5 metadata mismatch remains accepted for this first iteration. ## Test plan - npm run test:scripts - npm run lint - actionlint .github/workflows/generate-supported-versions.yml - diff coverage for every changed line and branch
Overall package sizeSelf size: 8.19 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.3.3 | 125.43 kB | 441.72 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 🎯 Code Coverage (details) 🔗 Commit SHA: 8296ea6 | Docs | Datadog PR Page | Give us feedback! |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #9763 +/- ##
========================================
Coverage 98.52% 98.52%
========================================
Files 975 975
Lines 143914 143914
Branches 12684 12510 -174
========================================
Hits 141797 141797
Misses 2117 2117 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:
|
BenchmarksBenchmark execution time: 2026-08-14 12:32:26 Comparing candidate commit 8296ea6 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 2265 metrics, 36 unstable metrics.
|
…-supported-versions
Declared instrumentation ranges remain the support contract, so CI version pins only select concrete tested versions and never cap an open range.
Generate
supported_versions.jsonfrom the supported Node.js range and the versions pinned by CI, with an optional narrower range for the workflow. Node.js built-ins usenode:module.Automatic updates only run for same-repository PRs targeting
master, excludev*.xheads, and only writesupported_versions.json. The known v5 metadata mismatch remains accepted for this first iteration.