Automated semantic versioning and release drafter

[zulissimeta]

• PRs now require a label for major/minor/patch to indicate what sort of release effect it will have. They can be retroactively labeled/relabeled
• PRs also require a label of enhancement/test/documentation/test/deprecation/dependencies to indicate what type of change it is.
• When code changes for one of the packages (core, data_oc, applications_cattsunami, demo_ocpapi), a draft release is created or updated if already exists. Only PRs that touch the package will be included. No other packages will be affected.
• Semantic versioning is used based on the largest of the included changes (major/minor/patch)
• On a release, the package affected will be released, and the docs will be built and deployed

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

[lbluque]

lgtm, thanks @zulissimeta!

Just to make sure I understand how releases will work:

1. On each push to main a release draft is made/updated based on the package that was changed in the merge.
2. Then when we are ready for release we need to tag the commit and push the tag. As long as the commit tag is the latest one on the draft that is automatically associated with the release on Github? Or do we need to do anything else?
3. Once the release is made on github, then the release.yml worfklow gets triggered.

Is the above correct?

[lbluque]

This file looks like a duplicate for this https://github.com/FAIR-Chem/fairchem/blob/main/.github/release.yml, right?

[lbluque]

can we exclude dependabot as well?