test before make a new release

[epassaro]

Description

• Run tests before making the release (we do not want to release broken software!)
• Use the tardis-bot endpoint
• Make pre-releases for dev versions

Motivation and context

How has this been tested?

• Testing pipeline.
• Other.

Examples

Type of change

• Bug fix.
• New feature.
• Breaking change.
• None of the above.

Checklist

• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • (optional) I have built the documentation on my fork following the instructions.
• I have assigned and requested two reviewers for this pull request.

[tardis-bot]

Before a pull request is accepted, it must meet the following criteria:

• Is the necessary information provided?
• Is this a duplicate PR?
  • If a new PR is clearly a duplicate, ask how this PR is different from the original PR?
  • If this PR is about to be merged, close the original PR with a link to this new PR that solved the issue.
• Does it pass existing tests and are new tests provided if required?
  • The test coverage should not decrease, and for new features should be close to 100%.
• Is the code tidy?
  • No unnecessary print lines or code comments.

[Rodot-]

Looks good to merge!

[codecov]

Codecov Report

Merging #1635 (5847346) into master (576038a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1635   +/-   ##
=======================================
  Coverage   67.13%   67.13%           
=======================================
  Files          73       73           
  Lines        6100     6100           
=======================================
  Hits         4095     4095           
  Misses       2005     2005           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 576038a...5847346. Read the comment docs.