v3.0.0

What's Changed

• chore: disable automated dependency updater config [incident-51602] by @moezein0 in #45
• ci: use github action that installs datadog-ci binary by @calvinbayer in #52

⚠️ Breaking Changes

1. Platform Requirements

IMPORTANT: This action now uses pre-built binaries. Supported platforms:

• ✅ linux-x64
• ✅ linux-arm64
• ✅ darwin-x64 (macOS Intel)
• ✅ darwin-arm64 (macOS Apple Silicon)
• ✅ win-x64 (Windows)

❌ Unsupported platforms (that worked in v2.x with npm):

• linux-arm (32-bit ARM)
• Other architectures where Node.js runs but datadog-ci binaries aren't built

If your workflows run on unsupported platforms, they will fail. Stick with v2.x, install datadog-ci directly, or request binary support from datadog-ci releases.

2. Removed node-version Input

The node-version parameter has been removed since Node.js is no longer required. If you're passing this parameter, you can safely remove it.

Before:

- uses: DataDog/junit-upload-github-action@v2
  with:
    node-version: "20"

After:

- uses: DataDog/junit-upload-github-action@v3
  # node-version removed

3. Default Version Changed

The default datadog-ci-version changed from "latest" to "v5".

Migration:

• If you want absolute latest: explicitly set datadog-ci-version: "latest" (deprecated, will show warning)
• Recommended: use datadog-ci-version: "v5" (latest v5.x) or pin to specific version like "v5.11.0"

🔄 Backwards Compatibility

To ease migration, legacy npm semver syntax still works but shows deprecation warnings:

• "latest" → "v5" ⚠️
• "^5.0.0" → "v5" ⚠️
• "~5.10.0" → "v5" ⚠️
• ">=5.0.0" → "v5" ⚠️
• "5.x" → "v5" ⚠️

Note: This backwards compatibility layer will be removed in v4.0.0. Please migrate to the new syntax.

🐛 Fixes

• Fixes #49: Supply chain risk with runtime npx install
• Fixes #31: Pin actions/setup-node to SHA (now completely removed)