v3.5.0

What's Changed

• Bump datadog-ci to v5.20.1 by @juan-fernandez in #62

Full Changelog: v3.4.0...v3.5.0

v3.4.0

What's Changed

• Bump datadog-ci to v5.18.0 by @juan-fernandez in #61

Full Changelog: v3.3.0...v3.4.0

v3.3.0

What's Changed

• Bump datadog-ci to v5.17.0 by @juan-fernandez in #60

Full Changelog: v3.2.0...v3.3.0

v3.2.0

What's Changed

• Bump datadog-ci to v5.16.1 by @juan-fernandez in #59

Full Changelog: v3.1.1...v3.2.0

v3.1.1

What's Changed

• Make action releases follow datadog-ci semver by @juan-fernandez in #55
• Use GitHub-generated release notes by @juan-fernandez in #56
• Consolidate action release flow around semver labels by @juan-fernandez in #57
• Fix datadog-ci major version resolution by @juan-fernandez in #58

Full Changelog: v3.1.0...v3.1.1

v3.1.0

What's Changed

• Pin the default datadog-ci-version to v5.14.0 and add local maintainer bump/release scripts by @juan-fernandez in #54

Maintainer Notes

• The default datadog-ci-version is now pinned to v5.14.0.
• RELEASE.md documents the local gh-based process for future datadog-ci bump PRs and action releases.

Full Changelog: v3.0.0...v3.1.0

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)

v2.2.0

What's Changed

• feat!: Update setup-node@v6 which uses node24 by @juan-fernandez and @kwngo in #42

New Contributors

• @kwngo made their first contribution

Full Changelog: v2.1.1...v2.2.0

v2.1.1

What's Changed

• Revert "feat: enable npm caching for datadog-ci dependency" by @juan-fernandez in #39

Full Changelog: v2.1.0...v2.1.1

v2.1.0

What's Changed

• feat: enable npm caching for datadog-ci dependency by @watson in #37

New Contributors

• @watson made their first contribution in #37

Full Changelog: v2.0.0...v2.1.0

What's Changed

• doc: improve auto-discovery option docs by @alexndlm in #26
• chore(ci): fix broken CI job by @watson in #36
• chore(ci): add Node.js v22-25 to CI test matrix by @watson in #35
• feat: enable npm caching for datadog-ci dependency by @watson in #37

New Contributors

• @alexndlm made their first contribution in #26
• @watson made their first contribution in #36

Full Changelog: v2.0.0...v2.1.0