Skip to content

Releases: benchmark-action/github-action-benchmark

v1.6.6

23 Dec 02:27

Choose a tag to compare

  • Fix: Parse floating numbers in the benchmark results from Benchmark.js. (Thanks @Bnaya)

v1.6.5

19 Dec 16:12

Choose a tag to compare

  • Fix: Titles are set to empty in auto-generated default index.html. To apply this fix, please remove current index.html in your GitHub Pages branch and run this action again
  • Fix: Skip fetching GitHub Pages branch before switching to the branch when skip-fetch-gh-pages is set to true
  • Improve: Explicitly note no action output from this action in README.md

v1.6.4

16 Dec 11:01

Choose a tag to compare

  • Fix: Supported actions/checkout@v2
  • Improve: Refactored index.html automatically generated when it does not exist
  • Improve: Update dependencies (actions/github v2)

v1.6.3

08 Dec 02:53

Choose a tag to compare

  • Improve: Tweak number of retries for more robust automatic git push

v1.6.2

07 Dec 12:05

Choose a tag to compare

  • Fix: Retry logic for git push did not work properly since stderr output was not included in error message

v1.6.1

07 Dec 11:42

Choose a tag to compare

  • Fix: Time unit of mean time in pytest benchmark results were always sec. Now time units are converted to msec, usec and nsec if necessary
  • Fix: Detecting rejection by remote on git push was not sufficient
  • Improve: Add a small link at right bottom of dashboard page to show this action provided the page
  • Improve: Showed at least 1 significant digit for threshold float values like 2.0
  • Improve: Updated dependencies

v1.6.0

04 Dec 13:01

Choose a tag to compare

  • New: fail-threshold input was added. Format is the same as alert-threshold, but you can give different thresholds to sending a commit comment and making the workflow fail by giving different value to fail-threshold from alert-threshold. This value is optional. If omitted, fail-threshold value is the same as alert-threshold
  • Improve: Retry logic was improved on git push failed due to remote branch updates after git pull. Now this action retries entire process to update gh-pages branch when the remote rejected automatic git push. Previously this action tried to rebase the local onto the remote but it sometimes failed due to conflicts

v1.5.0

30 Nov 11:26

Choose a tag to compare

  • New: Added max-items-in-chart input was added to limit the number of data points in a graph chart.
  • New: Supported Google C++ Benchmark Framework for C++ projects. Please check the example project and the example workflow to know the setup
  • Fix: Fix the order of graphs in the default index.html. To apply this fix, please remove index.html in your GitHub Pages branch and run your benchmark workflow again
  • Improve: Use the actions marketplace URL for the link to this action in commit comment
  • Improve: Updated dependencies
  • Dev: Added Many tests for checking the updates on a new benchmark result
  • Dev: Changed directory structure. Sources are now put in src/ directory

v1.4.0

23 Nov 15:42

Choose a tag to compare

  • New: external-data-json-path input was added to support to put benchmark data externally rather than Git branch
    • By using this input and actions/cache, you no longer need to use Git branch for this action if you only want performance alerts. Benchmark data is stored as workflow cache.
    • By this input, minimal setup for this action is much easier. Please read 'How to use' section in README.md.

v1.3.2

23 Nov 14:00

Choose a tag to compare

  • Improve: Styles in alert commit comment were improved
  • Fix: When benchmark name (with name input) contained spaces, URL for the workflow which detected performance regression was broken