Post-release workflow

[epassaro]

Description

The post-release workflow makes changes required after a release (huh).

• Updates the CHANGELOG.md (moved from pre-release job)
• Updates CITATION.cff

We can add more changes in the near future.

Motivation and context

How has this been tested?

• Testing pipeline.
• Other.

Everything was tested except the pull request job (very similar to the one in pre-release) and the release: trigger.

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 #2001 (7a2729c) into master (713c9db) will not change coverage.
The diff coverage is n/a.

❗ Current head 7a2729c differs from pull request most recent head cea576a. Consider uploading reports for the commit cea576a to get more accurate results

@@           Coverage Diff           @@
##           master    #2001   +/-   ##
=======================================
  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