v2.3.7

What's Changed

• README.md: Use current actions/setup-node and LTS version of Node.js by @cclauss in #247
• Update workflow to update and verify release branch by @afinetooth in #249

Bug Fixes

• Fixed fail-on-error behavior when download fails (#253), PR #254

New Contributors

• @cclauss made their first contribution in #247
• @Copilot made their first contribution in #254

Full Changelog: v2...v2.3.7

v2.3.6

What's Changed

• Explicitly set auto-detect as default for platform by @fredden in #240

Full Changelog: v2...v2.3.6

v2.3.5

What's Changed

• Automatically detect the platform to install by @fredden in #238
• README/Inputs: list all (non-deprecated) inputs by @jrfnl in #239

New Contributors

• @fredden made their first contribution in #238
• @jrfnl made their first contribution in #239

Full Changelog: v2...v2.3.5

v2.3.4

What's Changed

• Add coverage-reporter-platform input option by @afinetooth in #233
  • Since we have added support for coverage-reporter on aarch64, we need to provide users of our github-action the ability to select this architecture-specific version of coverage-reporter when they're using an aarch64 / arm64 runner in CI.

Full Changelog: v2...v2.3.4

v2.3.3

What's Changed

• Make sure the major version tag always points to the latest release (fixes #222) by @afinetooth in #230

Full Changelog: v2...v2.3.3

v2.3.2

What's Changed

• Verify that coverage-reporter-version option is recognized by @afinetooth in #229
• Add build-number to supported inputs options by @afinetooth and @brianatgather in #228
• Change sha256sum command flag to be compatible with alpine linux distros by @afinetooth and @jdebbink in #227
• Docs: Fix the action version in usage example by @Jeff-Tian in #210

New Contributors

• @brianatgather made their first contribution in #228 / #199
• @jdebbink made their first contribution in #227 / #198
• @Jeff-Tian made their first contribution in #210

Full Changelog: v2.3.1...v2.3.2

v2.3.1

What's Changed

Extend behavior of fail-on-error option to setup failures by @afinetooth in #226

• Technically an enhancement, these changes make the action behave as many customers already expect by ignoring any and all failures when the fail-on-error input is set to false.

• Adds logic to handle any failures in "setup" tasks, including downloading the coverage-reporter binary, verifying the binary, and finding the binary by its expected name after extraction.

• The new logic checks these actions and exits with code 1 on failure, except if fail-on-error is set to true, in which case it returns exit code 0.

• Adds a matrix workflow that tests the action for each os and the two key binary commands (coveralls report and coveralls done). Each of these scenarios implicitly tests our setup tasks since they run first in each scenario.

• Also extends the behavior of debug: true to flip the shell-specific debug flag for each os including set -x for linux and macos and Set-PSDebug -Trace 1 for windows.

Full Changelog: v2.3.0...v2.3.1

v2.3.0

What's Changed

• Set default values as strings per GH Action requirements by @littleforest in #204
• Allow pinning of coverage reporter version by @littleforest in #208

New Contributors

• @littleforest made their first contribution in #204

Full Changelog: v2.2.3...v2.3.0

v2.2.3

2.2.3: fix directory creation on Windows runners

v2.2.2

2.2.2: use pwsh for windows runner