Pre-release workflow

[epassaro]

Description

The pre-release workflow prepares TARDIS for a new release by just creating a single pull request to this repository:

• Runs scheduled (weekly) or manually
• Updates .zenodo.json metadata (no more need to writing directly to the protected master branch ❌💀)
• Updates CHANGELOG.md (and it works 😆 ) move to a post-release pipeline
• Creates .lock files according to TEP - 013
• Opens a PR to tardis-sn/tardis with all these changes
• A clear workflow for future file additions (like CITATION.cff, updated README.rst, etc.) move to a post-release pipeline

Then, if all checks pass, one of us should merge the pull request and an upcoming workflow should make the actual release.

Motivation and context

Make a more secure, robust release cycle.

How has this been tested?

• Testing pipeline.
• Other.

Tested on my fork and works as expected. In practice this workflow just creates a pull request, really safe to merge.

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.

[codecov]

Codecov Report

Merging #1989 (cc53945) into master (ae19f26) will not change coverage.
The diff coverage is n/a.

❗ Current head cc53945 differs from pull request most recent head 2a89ab2. Consider uploading reports for the commit 2a89ab2 to get more accurate results

@@           Coverage Diff           @@
##           master    #1989   +/-   ##
=======================================
  Coverage   59.99%   59.99%           
=======================================
  Files          70       70           
  Lines        8111     8111           
=======================================
  Hits         4866     4866           
  Misses       3245     3245           

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more